Hans Reiser wrote:
> Brad Boyer wrote:
> >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.
>
> Can you detail the problem?
>
The problem with the NetApp snapshots is that tar and cp and a few other
programs that check inode numbers get confused and think everything in
the snapshot is a hard link. So you can't copy a snapshot of a file back
over the original without copying it somewhere else first, and it's
painful to make an archive of the snapshots. We have data files on our
filers that get updated frequently, and any time I need to analyze the
same file over time, or restore an old file, it causes problems. I was
throwing it out more as an example of what sort of unexpected things
happen when you slightly change the way the filesystem works.
Brad Boyer
flar@allandria.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:28 EST