All of lore.kernel.org
 help / color / mirror / Atom feed
* RFE: per-subvolume timestamp that is updated on every change to a subvolume
@ 2015-01-05 17:27 Lennart Poettering
  2015-01-05 18:59 ` Goffredo Baroncelli
  2015-01-06  6:02 ` Qu Wenruo
  0 siblings, 2 replies; 4+ messages in thread
From: Lennart Poettering @ 2015-01-05 17:27 UTC (permalink / raw)
  To: linux-btrfs

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?

Lennart

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RFE: per-subvolume timestamp that is updated on every change to a subvolume
  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
  2015-01-06  6:02 ` Qu Wenruo
  1 sibling, 0 replies; 4+ messages in thread
From: Goffredo Baroncelli @ 2015-01-05 18:59 UTC (permalink / raw)
  To: Lennart Poettering, linux-btrfs

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RFE: per-subvolume timestamp that is updated on every change to a subvolume
  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
@ 2015-01-06  6:02 ` Qu Wenruo
  2015-01-06  8:13   ` Qu Wenruo
  1 sibling, 1 reply; 4+ messages in thread
From: Qu Wenruo @ 2015-01-06  6:02 UTC (permalink / raw)
  To: Lennart Poettering, linux-btrfs


-------- Original Message --------
Subject: RFE: per-subvolume timestamp that is updated on every change to 
a subvolume
From: Lennart Poettering <lennart@poettering.net>
To: <linux-btrfs@vger.kernel.org>
Date: 2015年01月06日 01:27
> 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?
In fact, btrfs_root_item contains one btrfs_inode_item, which contains 
the a/c/m/otime.
But not sure if it contains the time you need.

I'd better add acmotime output for inode_item in btrfs-debug-tree and 
try myself.

Thanks,
Qu
>
> 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?
>
> 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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RFE: per-subvolume timestamp that is updated on every change to a subvolume
  2015-01-06  6:02 ` Qu Wenruo
@ 2015-01-06  8:13   ` Qu Wenruo
  0 siblings, 0 replies; 4+ messages in thread
From: Qu Wenruo @ 2015-01-06  8:13 UTC (permalink / raw)
  To: Lennart Poettering, linux-btrfs


-------- Original Message --------
Subject: Re: RFE: per-subvolume timestamp that is updated on every 
change to a subvolume
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Lennart Poettering <lennart@poettering.net>, 
<linux-btrfs@vger.kernel.org>
Date: 2015年01月06日 14:02
>
> -------- Original Message --------
> Subject: RFE: per-subvolume timestamp that is updated on every change 
> to a subvolume
> From: Lennart Poettering <lennart@poettering.net>
> To: <linux-btrfs@vger.kernel.org>
> Date: 2015年01月06日 01:27
>> 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?
> In fact, btrfs_root_item contains one btrfs_inode_item, which contains 
> the a/c/m/otime.
> But not sure if it contains the time you need.
>
> I'd better add acmotime output for inode_item in btrfs-debug-tree and 
> try myself.
>
> Thanks,
> Qu
The value in acmotime of the inode_item in root_item is not used,
so it seems anyone can use it to record the acmotime for your purpose.

Thanks,
Qu
>>
>> 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?
>>
>> 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
>
> -- 
> 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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-01-06  8:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2015-01-06  6:02 ` Qu Wenruo
2015-01-06  8:13   ` Qu Wenruo

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.