Re: btrfs send/receive do not keep inode ctimes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jan + list

On Fri 131101, Jan Schmidt wrote:
> Hi Karl,
> 
> On Fri, October 25, 2013 at 15:12 (+0200), Karl Kiniger wrote:
> > is there low level support to change inode ctimes somehow?
> > (on ext[234] it can be done using debugfs)
> 
> No.

Yes :-), offline only of course

> 
> > It would be nice to make received snapshots as similar as
> > possible to their send source. (I am not talking about
> > uuids and such, just ls -lc output)
> 
> This is not planned. Currently, we do not even preserve the inode number. Can
> you give a short explanation of your use case, why do you need to keep the ctime?
> 
> Thanks,
> -Jan

I just wanted to clone a btrfs with many snapshots and at the same time
be able to mount both original and clone on the same computer.
(I did not even try because I dont know what kind of pain the duplicate
 uuids will cause)

Is there a known way to re-UUID such a cloned btrfs?

I don't really "need" the ctime, its just  convenient for looking whats
new in some folder - wget adjusts the mtime and unix/linux lacks the
"file creation time" time stamp.

Greetings,
Karl

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux