Hi,
On Mon, 3 Jul 2017, Petter Reinholdtsen wrote:
ls -l gives an input/output error when running on a directory containing
an .zfs directory (all run as root):
Are you sure you do not have corrupted disks? 'zpool status' should get
you going if that is the case.
Dit some more testst today.
Seems that input/output error is always popping up when ls -l directories
in the .zfs directory, which is read-only.
Built a new zfs array from other disks in the system and the same error
was consistently observed.
Accessing this directory with os.stats() from ipython, does not generate
any (detected) error message:
In [6]: for filename in os.listdir('.'):
...: print filename
...: print os.stat(filename)
...:
snapshot
posix.stat_result(st_mode=16749, st_ino=281474976710653, st_dev=39,
st_nlink=2, st_uid=0, st_gid=0, st_size=2, st_atime=1499183973,
st_mtime=1499183941, st_ctime=1499183941)
shares
posix.stat_result(st_mode=16749, st_ino=281474976710654, st_dev=39,
st_nlink=2, st_uid=0, st_gid=0, st_size=2, st_atime=1499183973,
st_mtime=1499178260, st_ctime=1499178260)
Compared to the shell:
ls -l
ls: snapshot: Input/output error
ls: shares: Input/output error
total 0
dr-xr-xr-x 2 root root 2 Jul 4 16:24 shares
dr-xr-xr-x 2 root root 2 Jul 4 18:00 snapshot
And of course zpool status gives No known data errors as output.
