All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Oleg Drokin <green@namesys.com>
Cc: Russell Coker <russell@coker.com.au>,
	ReiserFS <reiserfs-list@namesys.com>
Subject: Re: ReiserFS is not suitable for a root FS.
Date: Thu, 18 Sep 2003 13:50:01 +0200	[thread overview]
Message-ID: <3F699BE9.2090101@gmx.net> (raw)
In-Reply-To: <20030517121038.GA929@namesys.com>

Oleg Drokin wrote:
> Hello!
> 
> On Sat, May 17, 2003 at 02:01:00PM +0200, Carl-Daniel Hailfinger wrote:
> 
>>>>>With a ReiserFS file system you can't FSCK a file system that is mounted
>>>>>read-only.  This means that when a root file system needs to be FSCK'd
>>>>>you need to boot from installation media (or convert the swap space into
>>>>>a temporary root file system).
>>>>
>>>>I take this as a feature request. Right? It would certainly be nice to
>>>>have.
>>>
>>>Yes.
>>
>>Oleg? Given a statically linked reiserfsck binary completely loaded into
>>memory and an initrd below the reiserfs root filesystem, it should be
>>possible to completely unmount the root fs because the initrd is still
>>there and can serve as root fs.
>>In this situation, reiserfsck sould have no problems anymore because the
>>partition is not mounted at all.
>>
> 
> 
> Initrd is not always present, you know. And sticking 300k (dynamic) or 600k (static)
> reiserfsck in there is not all that fun probably.
> Our current idea is to check if fsck is going to repair the
> mounted partition and if this partition happens to contain the reiserfsck itself,
> then mlockall() is done to page in all the pages of executable
> (otherwise if we need to page something in in the middle of updating tree root pointer,
> we won't be able to find anythig and die) and then proceed as normal.

Any progress on this?

> This is still somewhat risky, though.
> And if fsck will die in the middle of repairing rootfs (which still can happen) (And say it was
> doing --rebuild-tree run), you won't be able to mount this fs anymore.


Regards,
Carl-Daniel


  parent reply	other threads:[~2003-09-18 11:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 10:30 ReiserFS is not suitable for a root FS Russell Coker
2003-05-17 10:56 ` Oleg Drokin
2003-05-17 11:09   ` Russell Coker
2003-05-17 11:24     ` Oleg Drokin
2003-05-17 11:32       ` Russell Coker
2003-05-17 11:40         ` Oleg Drokin
2003-05-17 11:14 ` Carl-Daniel Hailfinger
2003-05-17 11:25   ` Russell Coker
2003-05-17 12:01     ` Carl-Daniel Hailfinger
2003-05-17 12:10       ` Oleg Drokin
2003-05-19 10:22         ` Carl-Daniel Hailfinger
2003-05-19 10:31           ` Oleg Drokin
2003-05-21 22:09         ` Newsmail
2003-09-18 11:50         ` Carl-Daniel Hailfinger [this message]
2003-09-18 14:05           ` Vitaly Fertman
2003-05-17 12:40       ` Russell Coker
2003-05-19 19:55 ` bscott
2003-05-19 20:42   ` Dieter Nützel

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=3F699BE9.2090101@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=green@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=russell@coker.com.au \
    /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.