public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hedi Berriche <hedi@berriche.co.uk>
To: CN <cnliou9@fastmail.fm>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check refuses to work on readonly fs
Date: Tue, 1 Aug 2006 16:39:51 +0100	[thread overview]
Message-ID: <20060801153951.GB17036@linuxathome.me> (raw)
In-Reply-To: <1154433320.2160.267361956@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

Hi,

Based on the info you provided I infer that you're running Linux.

On Tue, Aug 01, 2006 at 14:00 CN <cnliou9@fastmail.fm> wrote:
| Hi!
|
| # init 1
| # mount -o ro,remount /
| # mount
| /dev/hda1 on / type xfs (rw)
| # xfs_check /dev/hda1
| xfs_check: /dev/hda1 contains a mounted and writable filesystem
|
| xfs_check/xfs_repair are willing to work only when I boot from a disk
| and check/repair the other unmounted disk.
|
| Why "mount" shows (rw) instead of (ro) even "mount -o ro,remount /" is
| issued?

Because mount is relying on /etc/mtab which couldn't be updated
precisely because / was remounted ro.

You'll need a recent xfsprogs version, at least 2.7.17 IIRC, one
that uses that uses /proc/mounts instead of /etc/mtab to check
filesystem status.

Or you can use a dirty and quick hack

    - prior to remounting ro, edit /etc/mtab and change the root fs entry from
    rw to ro.
    - remount ro
    - run your xfs_check/xfs_repair in dangerous mode.

FWIW the safe thing to do after a repair on a mounted root FS is to reboot.

Cheers,
Hedi.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-08-01 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 11:55 xfs_check refuses to work on readonly fs CN
2006-08-01 15:39 ` Hedi Berriche [this message]
2006-08-02 14:36   ` CN

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=20060801153951.GB17036@linuxathome.me \
    --to=hedi@berriche.co.uk \
    --cc=cnliou9@fastmail.fm \
    --cc=xfs@oss.sgi.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