From: Goffredo Baroncelli <kreijack@inwind.it>
To: Lennart Poettering <lennart@poettering.net>, linux-btrfs@vger.kernel.org
Subject: Re: RFE: per-subvolume timestamp that is updated on every change to a subvolume
Date: Mon, 05 Jan 2015 19:59:45 +0100 [thread overview]
Message-ID: <54AADF21.7060303@inwind.it> (raw)
In-Reply-To: <20150105172754.GC19126@gardel-login>
On 2015-01-05 18:27, Lennart Poettering wrote:
> Heya!
>
> I am looking for a nice way to query the overall last modification
> timestamp of a subvolume. i.e. the most recent mtime of *any* file or
> directory within a subvolume. Ideally, I think, there was a
> btrfs_timespec field for this in "struct btrfs_root_item", alas there
> isn't afaics. Any chance this can be added?
>
> Or is there another workable way to query this value? Maybe determine
> it from the current generation of a subvolume or so? Is that tracked?
> Ideas?
Did you tried with "btrfs subvolume find-new" ?
>
> Lennart
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2015-01-05 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 17:27 RFE: per-subvolume timestamp that is updated on every change to a subvolume Lennart Poettering
2015-01-05 18:59 ` Goffredo Baroncelli [this message]
2015-01-06 6:02 ` Qu Wenruo
2015-01-06 8:13 ` Qu Wenruo
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=54AADF21.7060303@inwind.it \
--to=kreijack@inwind.it \
--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 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.