From: Eric Sandeen <sandeen@redhat.com>
To: andrei.popa@i-neo.ro
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 discard does not apper in /proc/mounts
Date: Mon, 09 Jan 2012 11:12:24 -0600 [thread overview]
Message-ID: <4F0B1FF8.8010200@redhat.com> (raw)
In-Reply-To: <1325978619.4567.2.camel@ierdnac-hp>
On 1/7/12 5:23 PM, Andrei Popa wrote:
> Hello,
>
> ierdnac-hp ~ # cat /etc/fstab |grep discard
> /dev/sda3 / ext4
> discard,noatime,norelatime,barrier=0,errors=remount-ro,data=writeback
> 0 1
>
> ierdnac-hp ~ # tune2fs -l /dev/sda3|grep discard
> Default mount options: journal_data_writeback discard
>
> ierdnac-hp ~ # cat /proc/mounts |grep write
> /dev/root / ext4 rw,noatime,user_xattr,acl,barrier=0,data=writeback 0 0
>
>
What kernel?
If it's a recent kernel, here is the logic which controls whether to show it:
if (test_opt(sb, DISCARD) && !(def_mount_opts & EXT4_DEFM_DISCARD))
seq_puts(seq, ",discard");
i.e. if "discard" is in the default mount options for the fs, it is not
shown, by design - although I am not 100% sure why that design decision
was made; that logic was explicitly added here:
commit 8b67f04ab9de5d8f3a71aef72bf02c995a506db5
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sun Aug 1 23:14:20 2010 -0400
ext4: Add mount options in superblock
Allow mount options to be stored in the superblock. Also add default
mount option bits for nobarrier, block_validity, discard, and nodelalloc.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
which contained:
- if (test_opt(sb, DISCARD))
+ if (test_opt(sb, DISCARD) && !(def_mount_opts & EXT4_DEFM_DISCARD))
seq_puts(seq, ",discard");
so maybe Ted can speak to the reasoning behind it; I think the general philosophy
is to not show any defaults in /proc/mounts.
Thanks,
-Eric
next prev parent reply other threads:[~2012-01-09 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 23:23 ext4 discard does not apper in /proc/mounts Andrei Popa
2012-01-09 17:12 ` Eric Sandeen [this message]
2012-01-09 19:23 ` Andrei Popa
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=4F0B1FF8.8010200@redhat.com \
--to=sandeen@redhat.com \
--cc=andrei.popa@i-neo.ro \
--cc=linux-ext4@vger.kernel.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 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.