[Ocfs2-users] compile error on sles 11

Elliott Perrin elliott.perrin at tenzing.com
Tue May 4 09:58:59 PDT 2010


> -----Original Message-----
> From: ocfs2-users-bounces at oss.oracle.com [mailto:ocfs2-users-
> bounces at oss.oracle.com] On Behalf Of Sunil Mushran
> Sent: Tuesday, May 04, 2010 12:30 PM
> To: Werner Flamme
> Cc: ocfs2-users at oss.oracle.com
> Subject: Re: [Ocfs2-users] compile error on sles 11
> 
> On 05/04/2010 02:42 AM, Werner Flamme wrote:
> >
> > Thank you. Took a while to get this posting out of spam quarantine :-
> (
> > We had problems here for the last weeks :-(
> >
> > So, on the SLES10 where I succeeded in building the packages for
> ocfs2
> > and ocfs2-tools from source, I entered this command and got
> >
> > xsapora:~ # tunefs.ocfs2 -Q "%M %H %O\n" /dev/sda
> > backup-super strict-journal-super sparse inline-data unwritten
> >
> > Now I'm looking for the docs that should describe the features that
> are
> > implemented in the ocfs2 packages coming along with SLES10. I think I
> > failed, there are no docs for that, but I found
> > /usr/src/linux/Documentation/filesystems/ocfs2.txt. I don't see a
> list
> > of features, but only a list of lacking features:
> >
> 
> 
> Depends on the version of sles10. afair, sles10 sp1 ships equivalent
> of ocfs2 1.2. Meaning no sparse, inline-data, unwritten. sp2 ships the
> equivalent of 1.4 that has these features. Ping Novell support for
> more.
> 

>From my experience with OCFS2 on SLES10 SP2 do not use sparse on that platform. We experienced data corruption on every sparse allocation that we provisioned and many times data recovery was impossible after the corruption had occurred. 



More information about the Ocfs2-users mailing list