From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: filesystem corruption with 2.5.2-dj5
Date: Fri, 25 Jan 2002 19:25:00 +0100 [thread overview]
Message-ID: <E16UB25-0000L5-00@baldrick> (raw)
In-Reply-To: <E16U2Og-0000qu-00@baldrick> <15441.21347.214934.178562@harpo.it.uu.se>
In-Reply-To: <15441.21347.214934.178562@harpo.it.uu.se>
On Friday 25 January 2002 1:45 pm, Mikael Pettersson wrote:
> Duncan Sands writes:
> > I just gave 2.5.2-dj5 a try. On a subsequent reboot and fsck
> > (with a stable kernel), I got a slew of messages about bad inode
> > fsizes on files modified while using 2.5.2-dj5. The partition uses
> > ext2. This is a UP i386 (AMD K6) machine with no other patches.
> > What can I do to help track this down?
>
> I reported this a couple of hours ago for 2.5.3-pre and Al Viro posted
> this patch:
>
> --- C3-pre4/fs/ext2/ialloc.c Wed Jan 23 20:45:32 2002
> +++ /tmp/ialloc.c Thu Jan 24 21:41:52 2002
> @@ -392,6 +392,7 @@
> ei->i_flags &= ~(EXT2_IMMUTABLE_FL|EXT2_APPEND_FL);
> ei->i_faddr = 0;
> ei->i_frag_no = 0;
> + ei->i_frag_size = 0;
> ei->i_osync = 0;
> ei->i_file_acl = 0;
> ei->i_dir_acl = 0;
> --- C3-pre4/fs/ext2/inode.c Wed Jan 23 20:45:32 2002
> +++ /tmp/inode.c Thu Jan 24 21:44:48 2002
> @@ -963,6 +963,7 @@
> ei->i_frag_size = raw_inode->i_fsize;
> ei->i_osync = 0;
> ei->i_file_acl = le32_to_cpu(raw_inode->i_file_acl);
> + ei->i_dir_acl = 0;
> if (S_ISREG(inode->i_mode))
> inode->i_size |= ((__u64)le32_to_cpu(raw_inode->i_size_high)) << 32;
> else
Yes, that was the problem. Thanks for the info, I hadn't spotted the patch.
Duncan.
prev parent reply other threads:[~2002-01-25 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 9:11 filesystem corruption with 2.5.2-dj5 Duncan Sands
2002-01-25 12:45 ` Mikael Pettersson
2002-01-25 18:25 ` Duncan Sands [this message]
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=E16UB25-0000L5-00@baldrick \
--to=duncan.sands@math.u-psud.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox