[TriLUG] Partitioning recommendations

Andrew Perrin clists at perrin.socsci.unc.edu
Fri Jul 13 10:01:32 EDT 2007


I generally just make such disks /data0, /data1, etc., and then use 
symlinks to put stuff on them. I don't see a need for separate partitions 
unless you need them for system integrity (e.g., preventing /var from 
filling up / ).

andy

----------------------------------------------------------------------
Andrew J Perrin - andrew_perrin (at) unc.edu - http://perrin.socsci.unc.edu
Associate Professor of Sociology; Book Review Editor, _Social Forces_
University of North Carolina - CB#3210, Chapel Hill, NC 27599-3210 USA



On Fri, 13 Jul 2007, Jos Purvis wrote:

> ...but not quite the usual question. I have this-here big-ol' 320GB
> secondary disk that I just installed this morning in my workstation.
> It's intended to be reserved for backups (long story) of another
> machine, creating a local Yum repository...stuff like that. The OS is
> quite happy on its own 80GB disk, so I'm looking to just put, say,
> /opt on this one and slap all of the backup/repository/whatever
> storage under there.
>
> Here's my question: does it matter how I partition the disk? My first
> instinct was to just create one huge partition of 320GB, then I
> thought I should do something with LVM for fun, then I realized it's
> just one disk, so LVM would seem silly if I'm not creating multiple
> partitions. Is there any reason (performance or otherwise) not to just
> create one partition and move on? Am I overthinking this entirely?
> When making stewed tomatoes, are three enough? Are four too many?
>
> Thoughts?
>
>    --Jos
> -- 
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>



More information about the TriLUG mailing list