>
> That has not been my experience. I started with sles10 using ocfs2
with
> sparse files, and they were/are definitely sparse. I still have a
couple
> of the sles10 boxes running. I started with a 300 gb ocfs2 clustered
> between a couple xen servers and had a couple dozen domUs. I had to
add
> a second 300 gb ocfs2 volume as my domUs approached 30. My linux
domUs
> were logically 50gb. My total logical disk space being used on those
two
> 300 gb volumes was 1.3 tb. I would use the du -B1 -s commands to
> verify.
Interesting...I'll have to try, again. Maybe it changed mid-way
through the SLES10 versions or something like that.
>
> I only know all of this because of all the tracking/moving/recovering
I
> had to do when problems started. I also started tracking sizes in
> planning to go away from ocfs2 and away from spares files.
Again, I've had none of these issues. I have four production machines
accessing the same OCFS2 volume and have not ever had an issue with
corruption. My SAN is FC-attached to these hosts, but I have four more
hosts that I use for development and desktop support that are
iSCSI-attached to an Openfiler SAN, and I've not had any issues with the
iSCSI-attached OCFS2 volume, either.
>
> Either way, since I've moved most of my domUs off of ocfs2 my
> environment has been much more stable, so I'm almost definitely
getting
> away from ocfs2 and sparse files.
Interesting how different those experiences can be!
-Nick
--------
This e-mail may contain confidential and privileged material for the sole use
of the intended recipient. If this email is not intended for you, or you are
not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly
prohibited from downloading, photocopying, distributing or otherwise using this
message, its contents or attachments in any way. If you have received this
message in error, please notify us immediately by replying to this e-mail and
delete the message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither endorsed by nor
attributable to SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home