linux-kernel - Re: Versioning file system

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Jun 2007 22:00:31 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Trond Myklebust <trond.myklebust@....uio.no>
CC:	Bryan Henderson <hbryan@...ibm.com>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	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,
	viro@...iv.linux.org.uk
Subject: Re: Versioning file system

Trond Myklebust wrote:
>>
>> I assume NetApp flags the directory specially so that a POSIX directory 
>> read doesn't get it.  I've seen that done elsewhere.
> 
> No. 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.
> It means that you avoid all those nasty user issues where people try to
> hard link to/from .snapshot directories, rename files across snapshot
> boundaries, etc.
> 

Last I used a Netapp, it was configurable, I believe; I seem to also
vaguely remember that one could configure it so that it only was
accessible as part of a mount string rather than as part of an
already-mounted filesystem.  Of course, this was a long time ago.

	-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/