Newbie parbreastioning question 4357

That was *exactly* the reason symlinks, as opposed to hardlinks, were developed.

Then go to LVM. I don't mind symlinks at all though...

If something is going to just fill up a parbreastion, if there is only one parbreastion the system crashes. How serious the crash is depends, but it will not be fun, and essentially requires a reboot at a minimum.

On the other hand, if a parition, totally unused by the system, is made available via nfs and fills up, the system does not crash and the only effect is that the nfs mounted filesystem can't be written to. This will *never* require a reboot.

How do you know that? First, I do recall that the OP said "server", but I don't recall whether he restricted that to "file server" or not. Perhaps so, with only 256Mb of RAM.

But as noted above, it protects the system against problems with sharing files...

And since it is only 10.2 Gb, it might be pretty easy to run out of space.

What if he gets really smart, and wants to switch to Slackware?

Sigh... have you ever actually done any of this stuff???

What if he wants to share one filesystem with one host or group of hosts, and another with a different set of hosts? What if he wants one to be a different type of filesystem than another? The possibilities are endless!

For all of the many reasons stated above.

An insignificant fact though.

Right. It looks more like the "OP way". It appeared he had actually given it some real thought!

I don't think so, and I've been doing unix admin for a couple decades now.

--