I'm sure this has been discussed in the past. But its very hard to understand, or even patch incredibly advanced software such as ZFS without a deep understanding of the internals.
It will take quite a while before anyone can start understanding a file system which was developed behind closed doors for nearly a decade, and then released into opensource land via tarballs "thrown over the wall". Only until recently the source has become more available to normal humans via projects such as indiana. Saying "if you don't like it, patch it" is an ignorant cop-out, and a troll response to people's problems with software. On 7/30/09, "C. Bergström" <codest...@osunix.org> wrote: > Ross wrote: >> Supermicro AOC-SAT2-MV8, based on the Marvell chipset. I figured it was >> the best available at the time since it's using the same chipset as the >> x4500 Thumper servers. >> >> Our next machine will be using LSI controllers, but I'm still not entirely >> happy with the way ZFS handles timeout type errors. It seems that it >> handles drive reported read or write errors fine, and also handles >> checksum errors, but it's completely missed drive timeout errors as used >> by hardware raid controllers. >> >> Personally, I feel that when a pool usually responds to requests in the >> order of milliseconds, a timeout of even a tenth of a second is too long. >> Several minutes before a pool responds is just a joke. >> >> I'm still a big fan of ZFS, and modern hardware may have better error >> handling, but I can't help but feel this is a little short sighted. >> > patches welcomed > > ./C > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > -- Sent from my mobile device _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
