When you don't use redundant configuration (no mirror, no raidz, no
copies>1) then ZFS is going to panic on a write failure. It looks like
ZFS found a bad block on your disk.
Does SUN really say this about ZFS? Is this acceptable in a
production environment? What if one of your mirrored disk
fails and in the "degraded" environment (before you have had
a chance to replace the bad disk) ZFS discovers that a write
fails? Why can't it find an alternative block to write to?
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
Re: Big volumes, small files ... Though I don't have any direct experience with it, my impression is that people are using it in production systems successfully - so a description of your specific reservations would be useful. ... IIRC it occurs as part of an already-existing data copy operation at a very low level in the disk read/write routines, and at close to memory-streaming speeds. ... What can move at close to memory speeds is the *CPU* overhead involved in the checks, and it can piggyback on a memory-to-memory data move that is happening anyway. ... My impression is that *some* customers have workloads that have found ZFS to be very stable already, while others push corner cases that are still uncovering bugs. ... (comp.arch.storage)
Re: RELENG_7: zfs mirror causes ata timeout ...ZFS -- instead, it appeared to be specific to the motherboard I was ... these drives, ditto with an offline test? ... problem follows the disk. ... (freebsd-stable)
Re: Backup solution suggestions [ggated] ... from my end to the remote disk.....ZFS on top of it. ... Then I went on do do some geli test, geli'ed /dev/ggate0 and newfs'ed, mounted and played around a bit. ... If I can get that to work, then this would be a kickass solution (all encryption stuff works great, I don't have to allocate all space immediatly, I can expand it later without destroying data and starting from scratch etc). ... (freebsd-stable)
Re: Filesystem snapshots dog slow ... small filesystems, that are not busy. ... your disk is hammered making copies of all the cylinder ... groups, skipping those that are 'busy', and coming back to them later. ... This doesn't mean ZFS is ... (freebsd-hackers)
Re: Big volumes, small files ... The integrated integrity checking is extremely cpu intesive. ... There is no disk IO that is close to memory speeds. ...ZFS is great in design it is still new. ... I'm not sure I see how snapshots or journaling helps with backups.... (comp.arch.storage)
