Manoj Joseph wrote:
Michael Barrett wrote:
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 don't see how something like this can not be a bug. Don't tell me this
is a feature and UFS is working as per design! ;)
I'm just a user in this area so I cannot comment in the design. I guess
I figured if you run at 100% full for an unknown amount of time with
unknown system load where the root's kernel reserve is out of room, you
will see expected inode corruption. Granted there should be a mechanism
to fix the said corruption once the file system is unmounted.
Cheers
Manoj
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
