bug with TLA 313?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Updating to the latest TLA patch, I got odd issues just with "ls":

Example:

ls -al /beast/
ls: /beast/: No such file or directory
ls: /beast/.: No such file or directory
ls: /beast/lost+found: No such file or directory
ls: /beast/usr0: No such file or directory
ls: /beast/usr: No such file or directory
total 32
drwxr-xr-x  5 root root  4096 2007-07-13 16:18 .
drwxr-xr-x 27 root root  4096 2007-06-25 18:34 ..
drwx------  2 root root 16384 2007-06-25 17:08 lost+found
drwxr-xr-x 10 root root  4096 2007-06-18 13:31 usr
drwxr-xr-x 10 root root  4096 2007-06-18 13:31 usr0

I have one machine that is no longer returning from an "ls". I get other messages sometimes, not just "No such file or directory", but also "Bad file descriptor" or even "File exists". These extraneous messages are also occurring when copying from the GlusterFS to the GlusterFS. The files and directories mentioned do, in fact, exist, no matter what the extraneous error message says.

Is there a known issue with the current patchset?

Thanks,

Brent




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux