Robert Milkowski wrote On 11/08/06 08:16,:
Hello Paul,
Wednesday, November 8, 2006, 3:23:35 PM, you wrote:
PvdZ> On 7 Nov 2006, at 21:02, Michael Schuster wrote:
listman wrote:
hi, i found a comment comparing linux and solaris but wasn't sure
which version of solaris was being referred. can the list confirm
that this issue isn't a problem with solaris10/zfs??
"Linux also supports asynchronous directory updates which can make
a significant performance improvement when branching. On Solaris
machines, inode creation is very slow and can result in very long
iowait states."
I think this cannot be commented on in a useful fashion without
more information this supposed issue. AFAIK, neither ufs nor zfs
"create inodes" (at run time), so this is somewhat hard to put into
context.
get a complete description of what this is about, then maybe we can
give you a useful answer.
PvdZ> This could be related to Linux trading reliability for speed by doing
PvdZ> async metadata updates.
PvdZ> If your system crashes before your metadata is flushed to disk your
PvdZ> filesystem might be hosed and a restore
PvdZ> from backups may be needed.
you can achieve something similar with fastfs on ufs file systems and
setting zil_disable to 1 on ZFS.
There's a difference for both of these.
UFS now has logging (journalling) as the default, and so any crashes/power fails
will keep the integrity of the metadata intact (ie no fsck/restore).
ZFS has no problem either as its fully transacts both data and meta data
and should never see corruption with intent log disabled or enabled.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
