Site NavigationDisclaimerThe views or opinions expressed on this blog are my own and do not necessarily reflect the views or opinions of Oracle Corporation. The views or opinions expressed by visitors on this blog are theirs solely and may not reflect mine. Categories |
Wednesday, August 11. 2010Flexible storage handling using ZFS on Linux and OpenSolarisTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Currently ZFS doesn't have an fsck or the equivalent, at least in older versions of ZFS (probably the one in Linux, not sure about FreeBSD). Hence you can sometimes not open a zpool.
http://www.c0t0d0s0.org/archives/6071-No,-ZFS-really-doesnt-need-a-fsck.html has the details of the "zpool clear -F data" command that is a sort of fsck - just unwinds the last few transactions.
I'm probably going to start using ZFS, but it will have to be a version that includes this feature, i.e. http://www.c0t0d0s0.org/archives/6067-PSARC-2009479-zpool-recovery-a.html
Hi Richard, thanks for your comment! Indeed, there is no fsck for ZFS. But honestly, I never needed it so far - it seems to be quite difficult to corrupt ZFS in such a way that it does not recover by itself.
That's true, but there are still many people who found they couldn't open a zpool without complex zdb hacking - see the links in http://www.osnews.com/story/22423/Should_ZFS_Have_a_fsck_Tool_ (paragraph starting "The proof"). However, the PSARC mentioned, which is in OpenSolaris b134 (actually a bit earlier) and hence Nexenta 3.0+, seems to resolve this and removes need for an fsck.
|
QuicksearchCalendar
Show tagged entriesCreative Commons |
|||||||||||||||||||||||||||||||||||||||||||||||||