in-situ conversion to FT disk config?

Ben Scott dragonhawk at gmail.com
Tue Nov 15 23:00:01 EST 2005


On 11/15/05, Bill McGonigle <bill at bfccomputing.com> wrote:
> Is 'target' on a different filesystem?

  In the test I ran with that message, no.  I just repeated said test
across multiple filesystems.  Same behavior -- it appears to preserve
hard links onto the target filesystem.  That is on Whitebox 3.0r1.  I
also just tried it on FC4 with multiple filesystems; same behavior.

  Maybe it's a compile-time option or vendor-specific patch or some such thing?

> Last experience I had with this was on an FC3 with a disk used for
> rsnapshot backups - the hardlinks on that disk represent ~15 copies of
> the data, and when copying this filesystem to another disk cp ballooned
> all the hardlinks (1 copy of the data for each instance of a link).

  Hmmm.  *shrug*  I dunno.  Like I said, I never use hardlinks [1], so
I doubt I'd notice any problems.  A few extra inodes more or less gets
lost in the noise.

[1] And most of my professional work with Linux has been in
environments where most of the users were on 'doze anyway, so *they*
sure as hell don't use 'em.  :)

-- Ben



More information about the gnhlug-discuss mailing list