From: Suzuki <suzuki@in.ibm.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org,
reiserfs-list@namesys.com, akpm@osdl.org, suparna@in.ibm.com,
amitarora@in.ibm.com
Subject: Re: [BUG] Reiserfs: reiserfs_panic while running fs stress tests
Date: Fri, 12 May 2006 12:15:34 +0530 [thread overview]
Message-ID: <44642F0E.4050500@in.ibm.com> (raw)
In-Reply-To: <20060511105006.e4811957.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Fri, 05 May 2006 10:22:21 +0530 Suzuki wrote:
>
>
>>Hi,
>>
>>
>>I was working on a reiserfs panic with 2.6.17-rc3, while running fs
>>stress tests.
>
>
> Hi,
> What test(s) do you use?
The problem was initially hit while running the following tests
simultaneously..
IOZone, bonnie++, dbench, fs_inod, fs_maim, fsstress, fsx_linux,
postmark, tiobench.
As I had mentioned in my post, I have a simple testcase to trigger the
panic which can hit the code path explained below.
The root cause of the problem is (as mentioned in the earlier post):
Whenever there is an extending DIO write operation, the fs would
create a safe link so as to ensure the file size consistent, if there is
crash in between the DIO. This will be deleted once the write operation
finishes.
If the DIO write happens to go through a "HOLE" region in the file, it
will fall into normal "buffered write", which is done through the
address space operations prepare_write() & commit_write(). Now, the
prepare_write() might allocate blocks for the file (if needed). So if
there is some error at a later point (say ENOSPC) in prepare_write(), we
need to discard the allocated blocks. This is done by calling
"vmtruncate()" on the file. This call leads to reiserfs specific
truncate, which would try to add a save link for the file.
This addition causes a reiserfs_panic, since there is already a "save
link" stored for the file.
Thanks
Suzuki
>
>
>>The panic message looked like :
>>
>>" REISERFS: panic (device Null superblock): reiserfs[4248]: assertion
>>!(truncate && (REISERFS_I(inode)->i_flags & i_link_saved_truncate_mask)
>>) failed at fs/reiserfs/super.c:328:add_save_link: saved link already re
>>exists for truncated inode 13b5a "
>
>
> Thanks,
> ---
> ~Randy
next prev parent reply other threads:[~2006-05-12 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 4:52 [BUG] Reiserfs: reiserfs_panic while running fs stress tests Suzuki
2006-05-11 17:50 ` Randy.Dunlap
2006-05-12 6:45 ` Suzuki [this message]
2006-05-12 7:33 ` Vladimir V. Saveliev
2006-11-22 1:23 ` Suzuki
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=44642F0E.4050500@in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=akpm@osdl.org \
--cc=amitarora@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=suparna@in.ibm.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.