Date: Wed, 08 Mar 2006 15:11:47 -0600 From: Eric Anderson <anderson@centtech.com> To: Scott Long <scottl@samsco.org> Cc: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, Poul-Henning Kamp <phk@phk.freebsd.dk>, Ruslan Ermilov <ru@FreeBSD.org>, Kris Kennaway <kris@obsecurity.org>, Tor Egge <tegge@FreeBSD.org> Subject: Re: cvs commit: src/sys/ufs/ufs ufs_lookup.c Message-ID: <440F4893.2000400@centtech.com> In-Reply-To: <440F42A6.7000600@samsco.org> References: <1539.1141850573@critter.freebsd.dk> <440F42A6.7000600@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > Poul-Henning Kamp wrote: >> In message <440F3FAA.5090804@samsco.org>, Scott Long writes: >> >> >>> The only way to effectively avoid the problem would be to teach UFS to >>> completely ignore the '.snap' directory entry when doing a readdir and >>> lookup. That is not the same as what is being discussed with having a >>> special hiiden hint flag. >> >> >> Wouldn't that make it somewhat hard to actually access the snapshots ? >> > > Sorry, I meant that the dirent would be surpressed from normal lookups > and readdirs just just while it's unsafe to access it. That would mean that .snap is a hardcoded directory name, so if a user used .snapshots or some such name it would not obey the same principles, correct? Or would it be more of 'while snapshots are happening, ignore the directory containing the snapshot currently being created'? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440F4893.2000400>