Messages in this thread | | | Date | Sun, 4 Jan 2009 14:31:41 -0500 | From | Theodore Tso <> | Subject | Re: document ext3 requirements |
| |
On Sun, Jan 04, 2009 at 07:08:01PM +0000, Sitsofe Wheeler wrote: > Theodore Tso wrote: >> So what's the use case where people want to be able to mount a >> filesystem needing recovery read/only without running the journal? > > Corrupted SD card[1] that's been locked to read only for recovery > purposes without having the FS tear itself apart further?
In that case, the right answer is to copy the 32 GB SD card to hard drive, and then operate on the hard drive..... In general, if the media has started going bad, the *first* thing you want to do is an immediate copy of the media to some place stable.
> Others seem to be saying that it is useful for forensics...
Again, the best thing to do is a full image copy of the drive before you do anything else.....
If someone wants to implement code to scans the journal, and create a redirection map where whenever the filesystem needs to read from block N, it reads from block M instead, they should feel free to do so. But so far, each of the use cases people are talking about are pretty rare cases, which is probably why we don't have it at moment.
In fact, it's probably possible to create this as a pure userspace solution using devicemapper.
- Ted
| |