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
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46795F90.5030602@zytor.com>
Date:	Wed, 20 Jun 2007 10:10:40 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Bryan Henderson <hbryan@...ibm.com>
CC:	Trond Myklebust <trond.myklebust@....uio.no>,
	akpm@...ux-foundation.org, alan <alan@...eserver.org>,
	Chris Snook <csnook@...hat.com>,
	Jack Stone <jack@...keye.stone.uk.eu.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	viro@...iv.linux.org.uk
Subject: Re: Versioning file system

Bryan Henderson wrote:
>> The directory is quite visible with a standard 'ls -a'. Instead,
>> they simply mark it as a separate volume/filesystem: i.e. the fsid
>> differs when you call stat(). The whole thing ends up acting rather like
>> our bind mounts.
> 
> Hmm.  So it breaks user space quite a bit.  By break, I mean uses that 
> work with more conventional filesystems stop working if you switch to 
> NetAp.  Most programs that operate on directory trees willingly cross 
> filesystems, right?  Even ones that give you an option, such as GNU cp, 
> don't by default.
> 
> But if the implementation is, as described, wildly successful, that means 
> users are willing to tolerate this level of breakage, so it could be used 
> for versioning too.
> 
> But I think I'd rather see a truly hidden directory for this (visible only 
> when looked up explicitly).
> 

When I administered a bunch of netapps I remember turning the visible
.snapshots off.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ