From: Hans Reiser <reiser@namesys.com>
To: Brad Boyer <flar@pants.nu>
Cc: Andrew Pimlott <andrew@pimlott.ne.mediaone.net>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Nathan Scott <nathans@sgi.com>,
Andreas Gruenbacher <ag@bestbits.at>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@oss.sgi.com
Subject: Re: reiser4 (was Re: [PATCH] Revised extended attributes interface)
Date: Fri, 14 Dec 2001 14:10:57 +0300 [thread overview]
Message-ID: <3C19DE41.6000507@namesys.com> (raw)
In-Reply-To: <20011214051604.723C52B54A@marcus.pants.nu>
Brad Boyer wrote:
>Hans Reiser wrote:
>
>>I remember that I used to be a sysadmin with some NetApp boxes that have
>>a .snapshot directory that is invisible, and has special qualities.
>>
>>It worked. There were no namespace collision problems. None.
>>
>>These things can be survived by users.;-)
>>
>
>Yes, these things can be survived, but speaking as someone who currently
>has a job involving multiple NetApp boxes, I can say that the .snapshot
>directory has some seriously annoying properties that break tar and
>other programs that expect things to look normal. The snapshots have
>saved my ass a few times, but they're still a pain to work with due
>to a few little quirks. In particular, the files in the snapshot keep
>the same inode number as the actual file. Just remember that clever
>solutions that almost fit the traditional model can have strange
>results over time.
>
> Brad Boyer
> flar@allandria.com
>
>
>
Can you detail the problem?
Hans
next parent reply other threads:[~2001-12-14 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011214051604.723C52B54A@marcus.pants.nu>
2001-12-14 11:10 ` Hans Reiser [this message]
2001-12-14 15:06 ` reiser4 (was Re: [PATCH] Revised extended attributes interface) dmeyer
2001-12-14 21:23 ` Bernd Eckenfels
2001-12-14 18:27 ` Brad Boyer
2001-12-05 3:32 [PATCH] Revised extended attributes interface Nathan Scott
2001-12-07 20:20 ` Stephen C. Tweedie
2001-12-08 4:58 ` Nathan Scott
2001-12-08 20:17 ` Hans Reiser
2001-12-11 2:42 ` reiser4 (was Re: [PATCH] Revised extended attributes interface) Nathan Scott
2001-12-11 12:02 ` Hans Reiser
2001-12-11 19:23 ` Anton Altaparmakov
2001-12-11 21:21 ` Hans Reiser
2001-12-11 23:33 ` Anton Altaparmakov
2001-12-11 23:59 ` Hans Reiser
2001-12-12 2:16 ` Anton Altaparmakov
2001-12-12 12:02 ` Hans Reiser
2001-12-12 13:34 ` Anton Altaparmakov
2001-12-12 15:40 ` Hans Reiser
2001-12-13 1:43 ` Andrew Pimlott
2001-12-13 9:23 ` Hans Reiser
2001-12-13 15:27 ` Andrew Pimlott
2001-12-13 20:47 ` Hans Reiser
2001-12-13 21:01 ` Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C19DE41.6000507@namesys.com \
--to=reiser@namesys.com \
--cc=ag@bestbits.at \
--cc=aia21@cam.ac.uk \
--cc=andrew@pimlott.ne.mediaone.net \
--cc=flar@pants.nu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox