lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 11 Jun 2011 12:44:16 +0300 From: "Amir G." <amir73il@...rs.sourceforge.net> To: Alex Bligh <alex@...x.org.uk> Cc: Joe Thornber <thornber@...hat.com>, Lukas Czerner <lczerner@...hat.com>, Mike Snitzer <snitzer@...hat.com>, linux-ext4@...r.kernel.org, tytso@....edu, linux-kernel@...r.kernel.org, lvm-devel@...hat.com, linux-fsdevel <linux-fsdevel@...r.kernel.org> Subject: Re: LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots) On Sat, Jun 11, 2011 at 11:18 AM, Alex Bligh <alex@...x.org.uk> wrote: > > > --On 11 June 2011 08:49:08 +0100 Joe Thornber <thornber@...hat.com> wrote: > >> I am also convinced multisnap wont be suitable for every use case. > > I'm surprised by one thing ext 4 snapshots doesn't seem to do: I would have > thought the "killer feature" for doing snapshots in the fs rather than in > the block layer would be the ability to snapshot - and more importantly > roll back - only parts of the directory hierarchy. > > (I've only read the URLs Amir sent, so apologies if I've missed this) > No need for apologies. There is no per-directory snapshot nor rollback with ext4 snpshots. It is possible to configure a part of the directory hierarchy to be excluded from future snapshots, but not to delete it selectively from past snapshots. Amir. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists