From: Eric Sandeen <sandeen@redhat.com>
To: "Lars Täuber" <taeuber@bbaw.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: tune2fs -o noatime /dev/sd_
Date: Fri, 19 Dec 2008 09:19:50 -0600 [thread overview]
Message-ID: <494BBB96.5080207@redhat.com> (raw)
In-Reply-To: <20081219110114.aedf7b29.taeuber@bbaw.de>
Lars Täuber wrote:
> Sorry for the noise.
> Might have been a silly idea.
It's not silly, I can see where this might be very useful; but noatime
is applied at the vfs level and not at the filesystem level, so putting
the flag in the filesystem superblock on disk and propagating that back
up to the vfs at mount time might require a bit of trickiness to get
right & do cleanly, I'm not sure. I'll give it some thought.
It may be simpler & quicker to just tell your auto-mount framework to
mount certain devices, or labels, or uuids, or $WHATEVER with noatime if
you can? Of course that configuration is local to a single machine, and
doesn't travel with the drive...
-Eric
> Happy Christmas to you.
> Lars
>
> Lars Täuber <taeuber@bbaw.de> schrieb:
>> Hallo developers!
>>
>> I just would like to ask for a feature request for the ext[234] filesystems.
>> There are some usb-sticks used by me that are formated with ext2. All recent desktop enviroments let me mount them quiet easy but without the chance to tell them to mount it with the »noatime« option. But I liked them to be mounted with this option because of their flash characteristics.
>> It seems there is some space left for an EXT4_MOUNT_NOATIME option in ext4.h for all the ext[234] file systems.
>> What do you think about this?
>>
>> Thanks
>> Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-12-19 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 11:15 tune2fs -o noatime /dev/sd_ Lars Täuber
2008-12-19 10:01 ` Lars Täuber
2008-12-19 15:19 ` Eric Sandeen [this message]
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=494BBB96.5080207@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=taeuber@bbaw.de \
/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;
as well as URLs for NNTP newsgroup(s).