All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: ReiserFS List <reiserfs-list@namesys.com>
Cc: Joel Ebel <jbebel@ncsu.edu>
Subject: Re: read-only drive with reiserfs partiton not mountable
Date: Thu, 03 Jul 2003 19:27:52 +0200	[thread overview]
Message-ID: <3F046798.7070906@gmx.net> (raw)
In-Reply-To: <3F04668C.8090603@gmx.net>

[Sorry, I hit send a bit too early]
Carl-Daniel Hailfinger wrote:
> Joel Ebel wrote:
> 
>> Ok.  I've got an unusual problem.  My hard drive decided yesterday to
>>  turn read-only.  I can't write anything to it.  The data seems to be
>> all there and readable, but any write to the drive fails.  I have 
>> partitions of NTFS, FAT32, ext3, and reiserfs.  I'm able to mount all
>>  the other partitions and copy files off of them, but the reiserfs 
>> partition refuses to mount saying wrong fs type, bad superblock,
>> etc... Is there a reason that a reiserfs partition on a read-only
>> drive wouldn't mount?  I'd sure like to get what data I can off of
>> it.  Any ideas?
> 
> 
> Use UML (user-mode Linux) and arrange for writable backing store on 
> another fs.

To be more clear, the block device with reiserfs is the base for a COW
(copy on write) device which can be used under UML. For the writes, you
need to provide a file on a writable fs which will store the differences.
ReiserFS inside the UML will not notice the fact that you tricked it.

Carl-Daniel


-- 
http://www.hailfinger.org/


  parent reply	other threads:[~2003-07-03 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 17:09 read-only drive with reiserfs partiton not mountable Joel Ebel
     [not found] ` <3F04668C.8090603@gmx.net>
2003-07-03 17:27   ` Carl-Daniel Hailfinger [this message]
2003-07-03 20:44     ` Carl-Daniel Hailfinger
2003-07-06  2:25 ` Zygo Blaxell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F046798.7070906@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=jbebel@ncsu.edu \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.