Re: [Networker] Unix to Linux Migration

The same best practices regarding partitioning that apply to UNIX apply
to Linux.  Everything mounted to / is for desktop systems ... if even
for that.

If you want to avoid having multiple mount points for your oracle data
take a look at lvm.  In general overall io throughput should increase
having multiple block devices, as each device has its own device buffer.

Anyway, partition it like you would partition any *nix box and create
one lvm volume for oracle data. With that setup you can later add more
physical volumes to the volume group and resize your oracle volume to
grow it.
The only downside to lvm is that once you add physical volumes to an
existing volume group the space is concatenated rather than striped,
thus adding a single large disk to a volume group created with multiple
small disks may lead to performance issues for data located on the large
disk.

Fsck should not really be an issue since ext3 is a journaling
filesystem.
By default I believe it is configured to fsck twice a year or after 30
mounts whichever comes earlier (obviously it only does so when the
volume is being mounted).

> -----Original Message-----
> From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Librado Pamintuan
> Sent: Wednesday, May 10, 2006 9:25 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Unix to Linux Migration
> 
> Greetings,
> 
> We're setting up some Intel servers running Linux (Redhat) and I have
a
> question about logical volumes or partitioning schemes.
> The plan is to run Oracle databases on this platform as we transition
away
> from our unix environment.
> On the unix side we've always had multiple logical volumes where the
> oracle databases, applications etc. reside.
> That gives me multiple save sets when running backups but it also
means I
> need to micro-manage my disk more.
> It works but is more of a management task then we'd maybe like to have
to
> attend to.
> 
> Now on the linux side our disk (local SCSI at this point til we get
> something figured out) can be all be laid out under / and boot.
> Then the disk management is not really a concern until it gets full.
> 
> The server will be using a hardware RAID controller here also (likley
> RAID10) and the amount of storage I am talking about here is 350GB or
so
> per server.
> 
> So, I'm just wondering if anybody has any feedback on what they have
done
> as far as linux server partitoning, LVM etc.
> One thing I'm thinking about is if I have to run an 'fsck' on a
filesystem
> one large one will take much longer to complete.
> I do like the idea of using LVM as it means I don't have to know how
large
> to make my partitions ahead of time but there may be a performance
penalty
> attached.
> 
> Any feedback appreciated.
> 
> 
> Librado Pamintuan
> Technical Support Analyst II
> Information Systems Dep.
> Operations Group
> City of Regina
> 
> 
> Phone:          (306) 777-7573
> General Fax: (306) 777-6804
> eFax:             (306) 546-6002
> eMail:            lpamintuan AT regina DOT ca
> 
> 
> 
> <html><body><font face = "arial" size = "1">
> DISCLAIMER: The information transmitted is intended only
> for the addressee and may contain confidential,
> proprietary and/or privileged material. Any
> unauthorized review, distribution or other use
> of or the taking of any action in reliance upon
> this information is prohibited. If you received
> this in error, please contact the sender and
> 
> delete or destroy this message and any copies.
> </font><body></html>
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
> "signoff networker" in the
> body of the email. Please write to
networker-request AT listserv.temple DOT edu
> if you have any problems
> wit this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER