From: Fionn Behrens <fionn@spamfilter.de>
To: reiserfs-list@namesys.com
Subject: Re: Full of surprises - A reiser4 story from userland
Date: Wed, 28 Sep 2005 17:28:07 +0200 [thread overview]
Message-ID: <1127921286.12894.106.camel@laptop> (raw)
In-Reply-To: <200509281825.49873.vitaly@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
On Mi, 2005-09-28 at 18:25 +0400, Vitaly Fertman wrote:
> > 2.6.11 refused to boot the
> > root partition, claiming that there were an inconsistency in the FS.
>
> the disk format got new parameters and old kernels cannot understand it right.
Ah, I see. So maybe it would be a good idea if the new fs version would
put up a big fat warning to syslog when it detects a partition written
by a previous version, telling the user that he is about to break
compatibility to his older version (and that the must upgrade userland
tools, too!)
> > Sep 28 08:44:20 rtfm kernel: WARNING: wrong pset member (11) for 42
> > Sep 28 08:44:20 rtfm kernel: WARNING: unused space in inode 42
> which fsck version?
1.0.4
> > the man page said that this would be read-only.
>
> it says:
> " --check
> the default action checks the consistency and reports, but does not
> repair any corruption that it finds. This option may be used on a
> read-only file system mount.
> "
> it does not mean 100% read-only check.
Okay, you sound a bit like a lawyer, but: you right me wrong.
> > There was my fourth surprise: This fsck thing had LIED to me; it was not
> > read-only.
>
> why do you think --build-fs is read-only?
Had not gone --build-fs yet. This was still about --check.
> > It may have checked the fs read-only but it must have
> > treacherously flipped some "error" bit somewhere on disk
> > Warning, mounting filesystem with fatal errors, forcing read-only mount
> > (followed by the error from above)
>
> do you see anything relevant in the syslog?
That line was in the syslog.
> > So much for --check being just a check. I grabbed a book and lost about
> > two more precious working hours running the --build-fs thing.
> you need to clarify what reiser4progs version you are running.
> 1.0.5 fixes the fs to the letest format, which is needed for 2.6.13.
> 1.0.3 to the 2.6.10's one.
1.0.4 . As I am now back on 2.6.11, I guess I should not upgrade to
1.0.5 or would that not do harm anyway?
thanks for answering!
kind regards,
Fionn
--
I believe we have been called by history to lead the world.
G.W. Bush, 2002-03-01
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-28 15:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 13:40 Full of surprises - A reiser4 story from userland Fionn Behrens
2005-09-28 14:12 ` Domenico Andreoli
2005-09-28 14:51 ` Clemens Eisserer
2005-09-28 15:35 ` Fionn Behrens
2005-09-28 14:25 ` Vitaly Fertman
2005-09-28 14:51 ` Islam Amer
2005-09-28 15:56 ` Fionn Behrens
2005-09-28 18:13 ` Hans Reiser
2005-09-28 18:07 ` Hans Reiser
2005-09-28 15:28 ` Fionn Behrens [this message]
2005-09-28 15:57 ` David Masover
2005-09-28 18:32 ` Fionn Behrens
2005-09-28 19:13 ` Islam Amer
2005-09-28 19:52 ` iosched (was Re: Full of surprises - A reiser4 story from userland) Valdis.Kletnieks
2005-09-28 20:31 ` Islam Amer
2005-09-28 20:48 ` Hans Reiser
2005-09-28 20:32 ` Hans Reiser
2005-09-28 20:38 ` Islam Amer
2005-09-28 20:48 ` vs, can you port to 2.6.13 and put the port on our website as part of analyzing the latest patches added to the -mm series and their impact on reiser4 performance Hans Reiser
2005-09-29 15:05 ` Vladimir V. Saveliev
2005-09-29 0:55 ` iosched (was Re: Full of surprises - A reiser4 story from userland) David Masover
2005-09-29 1:22 ` michael chang
2005-09-29 9:34 ` Islam Amer
2005-09-29 18:47 ` David Masover
2005-09-29 19:01 ` Dan Oglesby
[not found] ` <5a59ce53050928143267c9d779@mail.gmail.com>
2005-09-28 21:33 ` studdugie
2005-09-28 22:20 ` Jonathan Briggs
2005-09-28 16:40 ` Full of surprises - A reiser4 story from userland Vitaly Fertman
2005-09-28 17:57 ` Fionn Behrens
2005-09-28 20:05 ` Vitaly Fertman
2005-09-28 18:11 ` Hans Reiser
2005-09-28 15:39 ` Ingo Bormuth
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=1127921286.12894.106.camel@laptop \
--to=fionn@spamfilter.de \
--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.