# Not able to access a directory

**URL:** <http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055>\
**Category:** HPC Technical\
**Created:** [September 23, 2020, 4:29pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055 "2020-09-23T16:29:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Azadeh.MoradinezhadDizgah](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/a/848f3c/32.png) [@Azadeh.MoradinezhadDizgah](http://hpc-community.unige.ch/u/Azadeh.MoradinezhadDizgah)\
**Post date:** [September 23, 2020, 4:29pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/1 "2020-09-23T16:29:37Z")

</div>

I am running a code on baobab. Today, all of a sudden I was unable to cd into the directory on my account where my code is. When I ls in my home directory, I get the following message  
ls: cannot access “directory name”: Communication error on send.

When I try to download some files from this directory on baobab to my local machine, I get the following error: Communication error on send

Can you advise me what to do. I am in a real panic mode, since I dont have a copy of my code anywhere else.

Thank you,  
Azadeh

---

<div class="post-metadata">

**Author:** ![Volodymyr.Savchenko](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/v/e99b99/32.png) [@Volodymyr.Savchenko](http://hpc-community.unige.ch/u/Volodymyr.Savchenko)\
**Post date:** [September 23, 2020, 5:05pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/2 "2020-09-23T17:05:43Z")

</div>

I have got the same issue. Two of my collaborators got it as well.

As a consolation, I suspect the data is just fine, since I also happen to have one shell which is already in the home directory, and in there I can view and even edit files. But I can not do “cd $PWD” which is funny.

Regards

Volodymyr

---

<div class="post-metadata">

**Author:** ![Azadeh.MoradinezhadDizgah](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/a/848f3c/32.png) [@Azadeh.MoradinezhadDizgah](http://hpc-community.unige.ch/u/Azadeh.MoradinezhadDizgah)\
**Post date:** [September 23, 2020, 5:23pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/3 "2020-09-23T17:23:41Z")

</div>

Thanks, so we just have to wait, but the files should be safe.

---

<div class="post-metadata">

**Author:** ![Volodymyr.Savchenko](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/v/e99b99/32.png) [@Volodymyr.Savchenko](http://hpc-community.unige.ch/u/Volodymyr.Savchenko)\
**Post date:** [September 23, 2020, 5:27pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/4 "2020-09-23T17:27:25Z")

</div>

That’s just my guess, but it seems so.

It is indeed unfortunate and it seems to be quite a critical issue, affecting likely all users and potentially breaking quite some jobs.  
But who knows.

V.

---

<div class="post-metadata">

**Author:** ![Luca.Capello](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/l/a9a28c/32.png) [@Luca.Capello](http://hpc-community.unige.ch/u/Luca.Capello)\
**Post date:** [September 23, 2020, 7:13pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/5 "2020-09-23T19:13:59Z")

</div>

Hi there,

> [@Azadeh.MoradinezhadDizgah](#):
>
> ls: cannot access “directory name”: Communication error on send.

One of the `beegfs-meta` servers segfaulted, I have restarted it (more investigation tomorrow during working time) and thus everything has been back to normal since 21:06, sorry for the inconvenience.

> [@Volodymyr.Savchenko](#):
>
> It is indeed unfortunate and it seems to be quite a critical issue, affecting likely all users and potentially breaking quite some jobs.  
> But who knows.

Two notes:

1. it was a software error, thus the files were safe.   
Moreover, given that we were talking about ${HOME} space, there are daily backups for everything except the ${HOME}/scratch symlink
2. not all the users were affected, but only those who were accessing files stored on the crashed server.   
However, there is no way to know in advance who is affected, given that ${HOME} (and ${SCRATCH} as well) are on BeeGFS, which is a distributed filesystem.

Again, sorry for the inconvenience.

Thx, bye,   
Luca

---

<div class="post-metadata">

**Author:** ![Volodymyr.Savchenko](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/v/e99b99/32.png) [@Volodymyr.Savchenko](http://hpc-community.unige.ch/u/Volodymyr.Savchenko)\
**Post date:** [September 23, 2020, 7:42pm UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/7 "2020-09-23T19:42:32Z")

</div>

> [@Luca.Capello](#):
>
> - it was a software error, thus the files were safe.  
> Moreover, given that we were talking about ${HOME} space, there are daily backups for everything except the ${HOME}/scratch symlink
> - not all the users were affected, but only those who were accessing files stored on the crashed server.  
> However, there is no way to know in advance who is affected, given that ${HOME} (and ${SCRATCH} as well) are on BeeGFS, which is a distributed filesystem.

So all three of our group users had the bad luck! It happens!

I confirm that all looks good for us now.

Thanks a lot!

Volodymyr

---

<div class="post-metadata">

**Author:** ![Yann.Sagon](http://hpc-community.unige.ch/user_avatar/hpc-community.unige.ch/yann.sagon/32/3_2.png) [@Yann.Sagon](http://hpc-community.unige.ch/u/Yann.Sagon)\
**Post date:** [September 24, 2020, 6:38am UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/8 "2020-09-24T06:38:02Z")

</div>

Dear @Volodymyr.Savchenko:

> [@Volodymyr.Savchenko](#):
>
> So all three of our group users had the bad luck! It happens!

BeeGFS a distributed storage, user’s files are spread on various servers and big files are stored by chunk on various servers. It means that as soon as you try to access a chunk of file or a file on the faulty server, you’ll face the issue. Sooner or later everyone is accessing all the Baobab storage servers.

Best

---

<div class="post-metadata">

**Author:** ![Azadeh.MoradinezhadDizgah](http://hpc-community.unige.ch/letter_avatar_proxy/v4/letter/a/848f3c/32.png) [@Azadeh.MoradinezhadDizgah](http://hpc-community.unige.ch/u/Azadeh.MoradinezhadDizgah)\
**Post date:** [September 24, 2020, 7:40am UTC](http://hpc-community.unige.ch/t/not-able-to-access-a-directory/1055/9 "2020-09-24T07:40:00Z")

</div>

Thank you for clarification and sorting out the issue. All looks good now.

Azadeh
