3 ms·
I'm running Nexenta / Solaris zfs with samba, but it supports accented characters just fine. Perhaps this is a limitation of Mac smb support. zfs also doesn't h
by barrkel 16y ago
I'm running Nexenta / Solaris zfs with samba, but it supports accented characters just fine. Perhaps this is a limitation of Mac smb support. zfs also doesn't have a repairing fsck as far as I know, but I have more faith in its monitoring and scrubbing features. It also bulk reads and writes at about 100mbytes a second, approaching the limit of gigabit ethernet.
- cynicalkane 16y agoZFS doesn't have a repairing fsck because it doesn't need one. The on-disk format uses a transactional design such that its always consistent, even if it fails in the middle of a write. AFIAK the only way to damage a zpool is if some snafu (one more serious than a mere write failure) wiped out a bunch of metadata together with the backup metadata all at the same time, but such an event would do very serious damage to any filesystem, which is why all important data should have an off-site backup.
- oomkiller 16y agoAnd now, you can even fix this with zpool import -F. It will find the last consistent transaction in the array and roll back to it. Saved my buddy's ass a few weeks ago when he went to replace a drive and accidentally pulled out 2 SATA connectors at once (on a raidz1).
- patrickgzill 16y agoYou can have it check the filesystem while it is online, by using "zpool scrub poolname" - it will go through and check all the ECC'd bits and then attempt to fix it if possible. You can then run "zpool status" and it will display the last time each pool was scrubbed, and show you the number of errors if any.