From: Edward Shushkin <edward@namesys.com>
To: system_lists@nullzone.org
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] Opss! on 2.5.6 with ReiserFS
Date: Sun, 10 Mar 2002 21:22:14 +0000 [thread overview]
Message-ID: <3C8BCE86.17A5F7E8@namesys.com> (raw)
In-Reply-To: <5.1.0.14.2.20020310165035.00caf5c0@192.168.2.131>
system_lists@nullzone.org wrote:
>
> Hi there,
>
> i got a 'Opss' on my PII (one of my fileservers) just changing the
> kernel version from 2.5.5 to .6
Reiserfs in linux >= 2.5.6-pre3 does have broken stuff in journal area due to vfs cleanups.
Please wait, or apply this:
--- linux-2.5.6-pre3/fs/reiserfs/journal.c.orig Thu Mar 7 12:44:43 2002
+++ linux-2.5.6-pre3/fs/reiserfs/journal.c Thu Mar 7 13:53:36 2002
@@ -1960,8 +1960,7 @@
SB_ONDISK_JOURNAL_DEVICE( super ) ?
to_kdev_t(SB_ONDISK_JOURNAL_DEVICE( super )) : super -> s_dev;
/* there is no "jdev" option and journal is on separate device */
- if( ( !jdev_name || !jdev_name[ 0 ] ) &&
- SB_ONDISK_JOURNAL_DEVICE( super ) ) {
+ if( ( !jdev_name || !jdev_name[ 0 ] ) ) {
journal -> j_dev_bd = bdget( kdev_t_to_nr( jdev ) );
if( journal -> j_dev_bd )
result = blkdev_get( journal -> j_dev_bd,
@@ -1976,9 +1975,6 @@
return result;
}
- /* no "jdev" option and journal is on the host device */
- if( !jdev_name || !jdev_name[ 0 ] )
- return 0;
journal -> j_dev_file = filp_open( jdev_name, 0, 0 );
if( !IS_ERR( journal -> j_dev_file ) ) {
struct inode *jdev_inode;
Thanks,
Edward
next parent reply other threads:[~2002-03-10 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 21:22 Edward Shushkin [this message]
2002-03-10 15:58 ` Opss! on 2.5.6 with ReiserFS system_lists
2002-03-10 18:37 ` [reiserfs-list] " system_lists
2002-03-11 6:40 ` Oleg Drokin
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=3C8BCE86.17A5F7E8@namesys.com \
--to=edward@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=system_lists@nullzone.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox