From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Cc: shaggy@austin.ibm.com
Subject: Linux 2.4.26 JFS: cannot mount
Date: Tue, 8 Jun 2004 21:56:10 +0200 [thread overview]
Message-ID: <20040608195610.GA4757@merlin.emma.line.org> (raw)
Hi,
this is a FYI bugreport. I acknowledge it doesn't contain useful
information for debugging, but in case there have already been related
reports, it may still be useful:
I recently had a mount failure for a jfs file system at boot-up, mount
complained about bad options or superblock, but no messages were stuffed
in dmesg.
Running fsck.jfs /dev/hda6 without further argument fixed this problem,
after fsck.jfs, I could mount the file system normally.
(fsck.jfs version 1.1.1, 17-Dec-2002)
Vanilla 2.4.26 kernel on SuSE Linux 8.2.
I haven't found any useful logs and didn't bother to dump the broken
file system image to tape or something because it struck a production
machine that needed to be brought back up quickly.
It is exported via NFS v2 and NFS v3 to Linux/x86 and Solaris 8/sparc64
clients.
The problematic file system was on an IBM IC35L060AVV207-0 drive that
was running with write cache switched off, it is an Athlon-XP 1700+
machine with 512 MB RAM and a VIA KT333 chip set that has been solid for
a long time.
The reboot that showed the mount error had been triggered by watchdog
that wasn't too happy that syslogd wasn't writing to /var/log/messages
(which was 2 GB sized after a looping process filled the disk)
Thanks for your attention,
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
next reply other threads:[~2004-06-08 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 19:56 Matthias Andree [this message]
2004-06-08 20:14 ` Matthias Andree
2004-06-08 20:36 ` Dave Kleikamp
2004-06-08 22:35 ` Matthias Andree
2004-06-09 0:12 ` Nathan Scott
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=20040608195610.GA4757@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®