All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Anders Widman <andewid@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Corrupted/unreadable journal: reiser vs. ext3
Date: Sat, 15 Feb 2003 16:23:47 +0300	[thread overview]
Message-ID: <20030215162347.A3598@namesys.com> (raw)
In-Reply-To: <2164549156.20030215140454@tnonline.net>

Hello!

On Sat, Feb 15, 2003 at 02:04:54PM +0100, Anders Widman wrote:
> > Ok, so probably we should make the following changes. The kernel set IO_ERROR
> > and FS_ERROR flags. 
> > In the case of IO_ERROR reiserfsck prints the message about hardware problems
> > and returns error, so the fs does not get mounted at boot. On attempt mounting
> > the fs with IO_ERROR flag set it is mounted ro with some message about hardware
> > problems. When you are sure that problems disappeared you can mount it with a
> > spetial option cleaning this flag and probably reiserfstune will have some
> > option cleaning these flags also.
> > In the case of FS_ERROR - search_by_key failed or beyond end of device access
> > or similar - reiserfsck gets -a option at boot, replays the journal if needed
> > and checks for the flag. No flag - returns OK. Else - run fix-fixable. Errors
> > left - returns 'errors left uncorrected' and the fs does not get mounted at
> > boot. On attempt mounting the fs with the flag just print the message about
> > mounting the fs with errors and mount it. Not ro here as kernel will not do
> > deep analysis of errors and it could be just a small insignificant error.
>   What  happens if there are FS errors on boot device? Not mounting ro

It get's mounted readonly first, then fsck will exit with appropriate error code,
then system will refuse to continue booting process, I presume ;)

>   will  make  system  inaccessible unless users has some other boot or
>   rescue media.

Sure, just like with any other filesystem.
If you want to avoid that, don't run fsck on your root device during boot,
or ignore what it have said to you ;)

>   Of  course, this  is  where  admins  should  have  another  disk  or
>   partition to boot and make FS repairs. :)

Actually it is possible to reiserfsck (readonly) mounted filesystem. The only
prerequisite I found is reiserfsck binary (built statically it seems, or
with all the libs) should be located on another fs (tmpfs works just fine for me).
And of course little bit of reiserfsck patching is needed ;)
That's how I repair broken root filesystems on our test-boxes when rootfs is getting
corrupt, because some moron\bclear guy have not created rescue partition in there
and I hate booting from CDs (And CDs usually have outdated reiserfsck anyway). 

Bye,
    Oleg

  reply	other threads:[~2003-02-15 13:23 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 20:05 Corrupted/unreadable journal: reiser vs. ext3 Dirk Schenkewitz
2003-02-13 22:49 ` Zygo Blaxell
2003-02-14  0:32   ` Hans Reiser
2003-02-14  8:18     ` Oleg Drokin
2003-02-14 10:13       ` Andreas Dilger
2003-02-14 10:17         ` Oleg Drokin
2003-02-14 10:50           ` Andreas Dilger
2003-02-14 10:59             ` Oleg Drokin
2003-02-14 13:34             ` Hans Reiser
2003-02-14 16:04               ` Rudy Zijlstra
2003-02-14 19:06               ` Andreas Dilger
2003-02-14 19:19                 ` Hans Reiser
2003-02-15 12:51                   ` Vitaly Fertman
2003-02-15 13:00                     ` Vitaly Fertman
2003-02-18 19:50                       ` Hans Reiser
2003-02-18 20:05                         ` Vitaly Fertman
2003-02-18 22:18                           ` Hans Reiser
2003-02-15 13:04                     ` Anders Widman
2003-02-15 13:23                       ` Oleg Drokin [this message]
2003-02-17 19:43                     ` Hans Reiser
2003-02-17 23:35                       ` Error <-> Partition Correspondance [was Re: Corrupted/unreadable journal: reiser vs. ext3] Manuel Krause
2003-02-18  6:54                         ` Oleg Drokin
2003-02-21  7:27                           ` Manuel Krause
     [not found]                             ` <20030221103757.B28866@namesys.com>
2003-02-21  8:22                               ` reiserfs messages cleanup patch Manuel Krause
2003-02-21  8:32                                 ` Oleg Drokin
2003-02-15 22:37                   ` Corrupted/unreadable journal: reiser vs. ext3 Andreas Dilger
2003-02-18  7:04                     ` fsck on boot (was: Re: Corrupted/unreadable journal: reiser vs. ext3) Ookhoi
2003-02-18 18:21                     ` Corrupted/unreadable journal: reiser vs. ext3 Hans Reiser
2003-02-18 19:22                       ` Oleg Drokin
2003-02-18 19:28                         ` Hans Reiser
2003-02-18 21:17                     ` Valdis.Kletnieks
2003-02-18 22:02                       ` Matthias Andree
2003-02-19  6:26                         ` Oleg Drokin
2003-02-18 22:23                       ` Hans Reiser
  -- strict thread matches above, loose matches on Subject: below --
2003-02-20  9:55 Dirk Schenkewitz
2003-02-20 10:20 ` Anders Widman
2003-02-17 10:04 Dirk Schenkewitz
2003-02-20  1:27 ` Juan Quintela
2003-02-20  9:03   ` Anders Widman
2003-02-14 14:30 Dirk Schenkewitz
2003-02-14 14:20 Dirk Schenkewitz
2003-02-14 20:58 ` Valdis.Kletnieks
2003-02-14  0:18 Sam Vilain
2003-02-23 23:31 ` Zygo Blaxell
2003-02-24  1:14   ` Anders Widman
2003-02-14  0:17 Sam Vilain
2003-02-14  0:16 Sam Vilain
2003-02-23 23:10 ` Zygo Blaxell
2003-02-12 20:57 Dirk Schenkewitz
2003-02-12 18:27 Anders Widman
2003-02-11 19:43 berthiaume_wayne
2003-02-12 10:48 ` Dirk Schenkewitz
2003-02-12 10:59   ` Hans Reiser
2003-02-12 11:24     ` Frank Baumgart
2003-02-12 11:35       ` Stefan Traby
2003-02-12 11:54     ` Dirk Schenkewitz
2003-02-12 12:42       ` Hans Reiser
2003-02-12 13:25         ` Dirk Schenkewitz
2003-02-12 16:22 ` Sam Vilain
2003-02-12 16:53   ` Anders Widman
2003-02-12 17:19     ` Hans Reiser
2003-02-12 17:40       ` Anders Widman
2003-02-12 18:15         ` Dirk Mueller
2003-02-12 18:20           ` Anders Widman
2003-02-12 18:20         ` Chris Dukes
2003-02-13 20:08   ` Zygo Blaxell
2003-02-11 18:59 Dirk Schenkewitz
2003-02-11 20:27 ` Hans Reiser
2003-02-11 21:30   ` Mike Hodson
2003-02-11 21:47     ` Hans Reiser
2003-02-11 21:58     ` Hans Reiser
2003-02-12  6:35       ` Oleg Drokin
2003-02-11 23:11     ` Adam Goryachev
2003-02-11 23:17       ` Anders Widman
2003-02-12  0:12         ` Hans Reiser
2003-02-12 10:23           ` Anders Widman
2003-02-12 10:47             ` Hans Reiser
2003-02-12 11:12               ` Adam Goryachev
2003-02-12 13:42                 ` Anders Widman
2003-02-12 14:15                   ` Russell Coker
2003-02-12 15:26                     ` Anders Widman
2003-02-12 16:22                       ` bscott
2003-02-12 16:28                       ` Russell Coker
2003-02-12 16:40                         ` Anders Widman
2003-02-13  3:42                       ` Zygo Blaxell
2003-02-13 10:13                         ` Anders Widman
2003-02-13 14:44                           ` Rudy Zijlstra
2003-02-13  3:31                     ` Zygo Blaxell
2003-02-12 16:39                 ` Sam Vilain
2003-02-12  5:12         ` Ross Vandegrift
2003-02-12  7:17         ` Oleg Drokin
2003-02-12 10:17         ` Alexander Lyamin
2003-02-12 10:19           ` Alexander Lyamin
2003-02-12 16:25         ` Vitaly Fertman
2003-02-12 16:56           ` Anders Widman
2003-02-12 17:13             ` Oleg Drokin
2003-02-12  1:02       ` Mike Hodson
2003-02-12  7:25         ` Oleg Drokin
2003-02-12  9:45         ` Hans Reiser
2003-02-12 16:09         ` Sam Vilain

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=20030215162347.A3598@namesys.com \
    --to=green@namesys.com \
    --cc=andewid@tnonline.net \
    --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.