Re: XFS / file system for backup server (Re: JFS / Unsupported file systems)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/29/08 06:32, hh.eu@gmx.de wrote:
> Ron Johnson wrote at 2008-04-29 11:34 +0200:
>> On 04/29/08 01:24, Alex Samad wrote:
>>>> On Mon, Apr 28, 2008 at 09:52:16PM -0500, Ron Johnson wrote:
>>>>> On 04/28/08 19:22, Alex Samad wrote:
>>>>> some reason that xfs is not being talked about?
>>>> We hate it because Dr. Evil uses it.
>>> has this got something to do with elderberries ?
>> A little, but not as much as you think...
>
> Hm, some of us, I am sure, have to look up what elderberries are in their
> language, conclude that they might have something to do with a
> shrubbery, but
> still do not quite get what you're talking about... :-)
>
> Anyway, are you just joking or are there serious reasons against XFS? I
> am not
Yes, it's just Austin Powers and Monty Python humor.
> very knowledgeable with respect to file systems on GNU/Linux, coming from a
> different background, and it's a few weeks ago that I made my decision so I
> don't remember all the details of my reasoning, but I have decided to
> try XFS
> for an rsync backup disk, mostly because it seemed to be the best choice
> for
> larger files and to hold metadata from different operating/file systems
> (extended attributes, ...).
That's the received wisdom. Back in the day, SGI (the people who
created xfs) were *the* last word in video processing, and so they
needed a filesystem tuned for very large files.
> I haven't implemented this in all detail and am currently testing it in
> various situation, so could change if you elaborated a bit or gave me
> pointers
> to resources on how to choose a good file system for a backup server
> holding
> data from several file systems.
>
> From this thread, XFS can cause trouble when it is not cleanly unmounted?
Yet more received wisdom. Better get a UPS!!!!!!
- --
Ron Johnson, Jr.
Jefferson LA USA
We want... a Shrubbery!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIFwsLS9HxQb37XmcRArqKAKDbezIqJi9FZi3MTpopoHPXVeFTBwCgsyoy
IqvWvpO3aGgZzqdXsNhDLPI=
=EtgO
-----END PGP SIGNATURE-----
Reply to: