From: Honza Fikar <j.fikar@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: no rw xfs file systems in mtab: /proc/mounts
Date: Thu, 23 Dec 2010 18:18:15 +0100 [thread overview]
Message-ID: <4D138457.8020008@gmail.com> (raw)
In-Reply-To: <4D13648B.8000105@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 1017 bytes --]
> hm that's a little confusing, what it means is it looked
> in /proc/mounts and did not find anything, or so it thought.
I agree that it's confusing, while there are xfs mounted rw in /proc/mounts
> As a result of:
>
> 89e4b5bd5615edc584a5111c86f12b4f89f8dd7d xfs_fsr: use /proc/mounts if available
I "quickly and dirty" tried to use /etc/mtab instead, but the result is
the same. Even tried some old version (3.0.3), which uses mtab and it's
the same.
> What does your /proc/mounts show?
it shows the lines included in the original e-mail, just here it is
wrapped, i.e. for the not working case:
>> ...
>> /dev/mapper/root / xfs
>> rw,noatime,attr2,inode64,logbufs=8,logbsize=256k,noquota 0 0
>> ...
and for working case:
>> ...
>> /dev/root / xfs
>> rw,noatime,attr2,delaylog,inode64,logbufs=8,logbsize=256k,noquota 0 0
>> /dev/mapper/encrypted /home xfs
>> rw,noatime,attr2,delaylog,inode64,logbufs=8,logbsize=256k,sunit=512,swidth=1536,noquota
>> 0 0
>> ...
Honza
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-23 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 12:32 no rw xfs file systems in mtab: /proc/mounts Honza Fikar
2010-12-23 15:02 ` Eric Sandeen
2010-12-23 17:18 ` Honza Fikar [this message]
2010-12-29 13:09 ` Christoph Hellwig
2011-01-10 15:55 ` Honza Fikar
2011-01-10 18:50 ` Christoph Hellwig
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=4D138457.8020008@gmail.com \
--to=j.fikar@gmail.com \
--cc=sandeen@sandeen.net \
--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