Re: "ls -d" OK, but not "ls"
On 2021-06-23 10:27:01 -0400, Greg Wooledge wrote:
> On Wed, Jun 23, 2021 at 03:59:51PM +0200, Vincent Lefevre wrote:
> > On a Debian GNU/Linux 10 (buster) machine:
> >
> > $ ls -ld /etc/systemd
> > drwxr-xr-x 3 root root 0 2021-04-19 09:40:41 /etc/systemd
>
> The "0" here is suspicious, and would be an indicator of wrongness
> if this is ext4.
>
> What type of file system is it?
aufs
> > $ ls /etc/systemd
> > ls: cannot open directory '/etc/systemd': No such file or directory
> >
> > Any explanation???
>
> If it's ext4, then my guess is "corrupted file system, fsck it".
>
> If it's btrfs or zfs, then my guess is "btrfs or zfs voodoo, consult
> a shaman".
And aufs?
Note: I am not the administrator of the machine (I have opened
a ticket, but I don't know when I will get an answer). However,
if there is something corrupt in the FS, I would have expected
this to be signaled by the kernel instead of getting ENOENT.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: