I managed to create a link in a ZFS directory that I can't remove. Session as
follows:
# ls
bayes.lock.router.3981 bayes_journal user_prefs
# ls -li bayes.lock.router.3981
bayes.lock.router.3981: No such file or directory
# ls
bayes.lock.router.3981 bayes_journal
Roger Fujii wrote:
I managed to create a link in a ZFS directory that I can't remove. Session
as follows:
# ls
bayes.lock.router.3981 bayes_journal user_prefs
# ls -li bayes.lock.router.3981
bayes.lock.router.3981: No such file or directory
# ls
bayes.lock.router.3981
I guess I should have included this output too:
# ls -al
total 124
drwx-- 2 rmf other 5 Aug 9 05:26 .
drwx--x--x 148 rmf other283 Aug 9 05:40 ..
-rw--- 1 rmf other 26616 Apr 16 00:17 bayes_journal
-rw--- 1 rmf other 1938 Apr 15
I managed to create a link in a ZFS directory that I can't remove.
# find . -print
.
./bayes_journal
find: stat() error ./bayes.lock.router.3981: No such
file or directory
./user_prefs
#
ZFS scrub shows no problems in the pool. Now, this
was probably cause when I was doing some
This is on a sol10u3 box. I could boot snv temporarily on this box if it
would accomplish something.
Maybe a kernel with a zfs compiled as debug bits would print
some extra error messages or maybe panic the machine when
that broken file is accessed?
Panic? That's rather draconian
Roger,
Could you send us (off-list is fine) the output of truss ls -l file? And
also, the output of zdb -vvv containing-filesystem? (which will compress
well with gzip if it's huge.)
thanks,
--matt
Roger Fujii wrote:
This is on a sol10u3 box. I could boot snv temporarily on this box if
