From: Ross Vandegrift <ross@willow.seitz.com>
To: Diego Calleja <grundig@teleline.es>
Cc: linux-kernel@vger.kernel.org, Jurgen Botz <jurgen@botz.org>
Subject: Re: Reiserfs corruption on 2.4.17-rc1!
Date: Tue, 18 Dec 2001 00:01:45 -0500 [thread overview]
Message-ID: <20011218000145.A15150@willow.seitz.com> (raw)
In-Reply-To: <20011217025856.A1649@diego> <13425.1008580831@nova.botz.org> <20011218003359.A555@diego>
In-Reply-To: <20011218003359.A555@diego>; from grundig@teleline.es on Tue, Dec 18, 2001 at 12:33:59AM +0100
> This is my opinion:
> -Something (reiserfs, anything) has caused fs corruption
> -It should be repaired by reiserfsck, but it's broken :-((
> -This corruption should NOT have happened, reiserfsck shouldn't
> have to be used.
> -I'm not a kernel hacker, so I can't try anything...what I know is
> that
> /etc in hc5 doesn't work. /usr, /var....works correctly.
>
> Well, I'd like to know what's happened in my drive. Can somebody try to
> give an explanation?
I've seen this happen when being careless about partitioning my drive. If
you changed your partition table and created the filesystem without a reboot
you could be in for this problem. If fdisk was unable to update the
partition table after writing it out and you ran mkreiserfs, you just made a
filesystem on the *old* partition, according to the *old* partition table.
Upon rebooting, the disk will be synced to the new partition table. If you
happened to shrink the parition a bit, the filsystem is suddenly longer than
the partition.
Ross Vandegrift
ross@willow.seitz.com
next prev parent reply other threads:[~2001-12-18 5:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 17:48 Reiserfs corruption on 2.4.17-rc1! Diego Calleja
2001-12-16 17:57 ` Diego Calleja
2001-12-16 20:12 ` Ragnar Kjørstad
2001-12-17 1:58 ` Diego Calleja
2001-12-17 21:01 ` Sakari Ailus
[not found] ` <13425.1008580831@nova.botz.org>
2001-12-17 23:33 ` Diego Calleja
2001-12-18 5:01 ` Ross Vandegrift [this message]
2001-12-18 6:19 ` Jurgen Botz
2001-12-18 21:45 ` Diego Calleja
[not found] ` <15391.12150.650359.33792@laputa.namesys.com>
[not found] ` <20011218220828.A381@diego>
2001-12-18 21:11 ` [grundig@teleline.es: Re: Reiserfs corruption on 2.4.17-rc1!] Diego Calleja
2001-12-19 9:18 ` Nikita Danilov
[not found] ` <3C1F3FDA.5050601@namesys.com>
2001-12-18 21:35 ` [reiserfs-list] Re: Reiserfs corruption on 2.4.17-rc1! Diego Calleja
[not found] ` <20011218125852.A1159@namesys.com>
[not found] ` <20011218224848.C377@diego>
[not found] ` <20011219095303.A11409@namesys.com>
2001-12-20 0:20 ` Diego Calleja
[not found] <20011217002350.D418@diego>
2001-12-17 1:45 ` Diego Calleja
2001-12-19 16:56 ` Edward Muller
2001-12-19 22:17 ` Diego Calleja
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=20011218000145.A15150@willow.seitz.com \
--to=ross@willow.seitz.com \
--cc=grundig@teleline.es \
--cc=jurgen@botz.org \
--cc=linux-kernel@vger.kernel.org \
/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.