From: Martin Steigerwald <Martin@lichtvoll.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Lennart Poettering <lennart@poettering.net>,
dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: btrfs_inode_item's otime?
Date: Sat, 10 Jan 2015 11:13:52 +0100 [thread overview]
Message-ID: <8849914.dEW4UQEyXo@merkaba> (raw)
In-Reply-To: <20150107144250.GA2901@infradead.org>
Am Mittwoch, 7. Januar 2015, 06:42:50 schrieb Christoph Hellwig:
> On Wed, Jan 07, 2015 at 02:57:35PM +0100, Lennart Poettering wrote:
> > Exposig this as xattr sounds great to me too.
>
> NAK - exposing random stat data as xattr only creates problems.
>
> Given that we don't seem to be able to get a new stat format anytime
> soon we should add a generic ioctl to expose it, reading it from struct
> kstat which all filesystem that support this attribute should fill out.
> And there's quite a lot of them.
What is the issue with the xstat, new stat format stuff? Basically I have the
feeling that this is in discussion for at least 5 years or so and I always
wondered where it is stuck. I am not aware of any discussions of it recently,
but I may have overseen those.
Ext4, I think, already supports birth time, but cannot expose it either. And
even the stat command already seems to have some support for it, except that
it doesn´t work yet (this is on BTRFS, but on Ext4 its the same).
merkaba:~> LANG=C stat /bin/ls
File: '/bin/ls'
Size: 118280 Blocks: 232 IO Block: 4096 regular file
Device: 14h/20d Inode: 3574391 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2014-10-31 11:29:37.000000000 +0100
Modify: 2014-10-30 03:43:06.000000000 +0100
Change: 2014-10-31 11:29:41.440773090 +0100
Birth: -
Any pointers?
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2015-01-10 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 17:21 btrfs_inode_item's otime? Lennart Poettering
2015-01-06 11:47 ` Chris Samuel
2015-01-06 12:43 ` Chris Samuel
2015-01-06 18:41 ` David Sterba
2015-01-08 10:52 ` Chris Samuel
2015-01-09 16:11 ` David Sterba
2015-01-15 10:48 ` David Sterba
2015-01-16 4:47 ` Chris Samuel
2015-01-06 18:26 ` David Sterba
2015-01-07 13:57 ` Lennart Poettering
2015-01-07 14:42 ` Christoph Hellwig
2015-01-10 10:13 ` Martin Steigerwald [this message]
2015-01-10 10:17 ` 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=8849914.dEW4UQEyXo@merkaba \
--to=martin@lichtvoll.de \
--cc=dsterba@suse.cz \
--cc=hch@infradead.org \
--cc=lennart@poettering.net \
--cc=linux-btrfs@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 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).