From: Bill Wilken <bill.wilken@comcast.net>
To: reiserfs-list@namesys.com
Subject: Apparent fsck failure ...
Date: Thu, 18 Aug 2005 15:07:40 -0400 [thread overview]
Message-ID: <1124392060.12959.5.camel@linux.site> (raw)
I am running Suse 9.3, 32-bit, on an Athlon-64 CPU (my 2800-series cpu
won't support the 64-bit product) with 1GB RAM, a 40GB hard drive
(dev/hda2), and a DVD/RW. Suse tells me that I must run fsck manually
because dev/hda2 is mounted with write permissions (See below) Why
wouldn't you mount a hard drive partition with write permissions?
linux:/home/wilkenw # fsck -CV
fsck 1.36 (05-Feb-2005)
Checking all file systems.
[/sbin/fsck.reiserfs (1) -- /] fsck.reiserfs /dev/hda2
reiserfsck 3.6.18 (2003 www.namesys.com)
*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************
Will read-only check consistency of the filesystem on /dev/hda2
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
###########
reiserfsck --check started at Thu Aug 18 15:00:39 2005
###########
Partition /dev/hda2 is mounted with write permissions, cannot check it
fsck.reiserfs /dev/hda2 failed (status 0x10). Run manually!
next reply other threads:[~2005-08-18 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 19:07 Bill Wilken [this message]
2005-08-18 19:57 ` Apparent fsck failure michael chang
2005-08-18 20:14 ` Bill Wilken
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=1124392060.12959.5.camel@linux.site \
--to=bill.wilken@comcast.net \
--cc=reiserfs-list@namesys.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.