Michael Barrett wrote:
Robert Milkowski wrote:
Hello Michael,
Sunday, May 27, 2007, 5:13:39 AM, you wrote:
MB> Does ZFS handle a file system full situation any better than UFS?
I had
MB> a ZFS file system run at 100% full for a few days, deleted out the
MB> offending files to bring it back down to 75% full, and now in
certain MB> directories I cannot issue a ls -la (it hangs) but a ls
works fine. MB> Normally in UFS this meant one would need to run a
fsck. What does one
MB> do for ZFS?
1. I've never run at a bug tat after ufs was 100% you need to fsck -
perhaps there's another problem?
Normally if you have a ufs file system hit 100% and you have a very high
level of system and application load on the box (that resides in the
100% file system) you will run into inode issues that require a fsck and
show themselves by not being about to long list out all their attributes
(ls -la). Not a bug, just what happens.
I've done extensive testing of this condition and have never found a need
for fsck. Can you reproduce this? If so, then please file a bug!
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
