| |||||||||||||
Maybe btrfs has no fsck,Maybe btrfs has no fsck,Posted Jun 17, 2009 21:36 UTC (Wed) by anselm (subscriber, #2796)In reply to: Maybe btrfs has no fsck, by drag Parent article: What ever happened to chunkfs?
What I've heard about the Reiserfs fsck is that it will, among other issues, mistake a file system superblock in the middle of a partition for the start of a whole new file system and get thoroughly confused. With virtualisation in widespread use and people keeping file system images in files this is more of a problem than it used to be when Reiserfs was new. If this is actually true, it is one more reason to bury Reiserfs deeply, with a wooden stake driven through its heart.
(Log in to post comments)
Maybe btrfs has no fsck, Posted Jun 18, 2009 8:46 UTC (Thu) by pcampe (guest, #28223) [Link]
I vaguely remember the problem you have described, something like a report from a key kernel developer; I am not sure it was ReiserFS the file system, nor if a workaround has been implemented.
Maybe btrfs has no fsck, Posted Jun 18, 2009 11:33 UTC (Thu) by nye (guest, #51576) [Link]
That was basically FUD. In reiserfsck there's an option to rebuild the filesystem entirely - you're essentially telling it 'this filesystem is trashed; just look through the disk for anything that might be a valid filesystem structure and cobble it together if you can'.
The 'problem' of mistaking a superblock in some image you have somewhere for the start of a new fs is *exactly what you asked it to do*, so those who complained so loudly about it really have nobody to blame but themselves.
It'll be funny if it was not so sad Posted Jun 18, 2009 12:16 UTC (Thu) by khim (subscriber, #9252) [Link] The 'problem' of mistaking a superblock in some image you have somewhere for the start of a new fs is *exactly what you asked it to do*, so those who complained so loudly about it really have nobody to blame but themselves. Yup. They did one mistake, but that mistake was grave: they assumed they can trust reiserfs. I've seen few cases where tiny nimber of badblocks killed reiserfs completely: nothing except this "cobble it together if you can" option worked and "cobbled together" filesystem was a mess (because there were some virtual images on that filesystem). Note: this exactly type of corruption SSD shows in real world. If reiserfs's "gentle" fsck does not work and if "last resort" approach is unusable then the only solution is to switch to other filesystem...
It'll be funny if it was not so sad Posted Jun 18, 2009 16:29 UTC (Thu) by nye (guest, #51576) [Link]
Meh, the only FS I've ever lost data to - aside from understandably unrecoverable data on damaged disk blocks - was XFS[0], and I used reiser3 extensively until a couple of years ago when it was obvious that ship had sailed.
Perhaps I merely got lucky with my disks not failing in exactly the wrong way, but there's always going to be an anecdote for everything.
[0](it's certainly the only FS that I actively despise, and would unreservedly recommend against in all circumstances)
The problem is: disk DO fail and reiserfs is TOTALLY unready Posted Jun 19, 2009 10:58 UTC (Fri) by khim (subscriber, #9252) [Link] Meh, the only FS I've ever lost data to - aside from understandably unrecoverable data on damaged disk blocks But the bad blocks DO exist in real life - you can not just ignore them! Reiserfs design NEVER ever considered this facet of life: if you have ONE bad block in wrong place - you are screwed 100%. When disk size is 512 bytes and HDD size of 2TiB loss of a 0.0000000003% of your data means 100% of your stuff is lost. This is not even funny. XFS is also not a good idea (I was biten by it too) - but here we have bad implementation, not bad design. Implementation can be fixed, design mistake is unfixable.
The problem is: disk DO fail and reiserfs is TOTALLY unready Posted Jun 22, 2009 16:22 UTC (Mon) by nye (guest, #51576) [Link]
>But the bad blocks DO exist in real life - you can not just ignore them!
I certainly don't disagree; I was referring to the data actually on the damaged part of the disk, which I wouldn't reasonably expect to be able to recover without great expense.
It'll be funny if it was not so sad Posted Jun 21, 2009 6:47 UTC (Sun) by cventers (subscriber, #31465) [Link]
I was a reiser3 user for quite a while and often sung its praises. A few
years into that stretch, my PC started having stability problems which I tracked to bad RAM.
I caught the bad RAM pretty quickly, and considered myself lucky that I
However, replacing the RAM didn't solve the stability problem. The nature
After a couple of big scares with "md" after the system had randomly
My full filesystem backup became handy after I was unable to bring the
Sadly, I lost the filesystem a few more times and burned even more time
My system never froze again.
I don't know enough about the reiserfs design to know how plausible my
There's a shocking bit of irony in this particular failure mode. Because
|
|||||||||||||