Mailinglist Archive: opensuse (3336 mails)
| < Previous | Next > |
Re: [SLE] Reiser4 in SuSE 10.0 - corruption issues.
- From: kanenas@xxxxxxxxxxxxx
- Date: Wed, 14 Dec 2005 08:55:30 -1000
- Message-id: <200512140855.30265.kanenas@xxxxxxxxxxxxx>
I must apologize for posting to the wrong thread.
sorry!
On Wednesday 14 December 2005 08:40, kanenas@xxxxxxxxxxxxx wrote:
> Thanks, that did it. Actually I also disabled kwallet in the geneneral
> settings as well (the other tab besides access controls), have not seen
> anything adverse yet...
> d.
>
> On Wednesday 14 December 2005 07:05, Andrei Verovski (aka MacGuru) wrote:
> > Hi,
> >
> > Have you formatted your RAID volume as Reiser4 root? BTW, did you compile
> > Reiser4 support into SuSE kernel yourself?
> >
> > On Wednesday 14 December 2005 12:21, Sbs Bofh wrote:
> > > SuSE 10.0 ships with Reiser4 support as optional packages (
> > > reiser4progs-1.0.4-2 and libaal-1.0.4-2). I'm aware that Reiser4 is
> > > not in the stock kernel yet and that its inclusion seems to be a
> > > slightly contentious issue.
> > >
> > > ...however...
> > >
> > > on a test machine I've been putting Reiser4 through its paces. The box
> > > is AMD64-powered, boots from an IDE drive and has a 3ware RAID
> > > controller with 4x 300GB drives, as a RAID5 array w/ hot spare. The
> > > entire /dev/sda device was set up in to LVM2 and there's a 838GB
> > > Reiser4 filesystem on it.
> > >
> > > So far, so good. I've loaded hundreds of GB of data and set up a
> > > mailserver with Maildirs and I have to say the performance is
> > > impressive.
> > >
> > > EXCEPT, I get fairly regular corruption on the Reiser4 filesystem,
> > > which can only be fixed with a "fsck.reiser4 --build-fs" (although it
> > > does fix the corruption and I haven't yet found any evidence of lost
> > > data - lost+found is always empty).
> > >
> > > After contacting Vitaly Fertman at Namesys for assistance it appears
> > > that this is due to an issue with "plugin set fields" (his words) in
> > > the 1.0.4version of the Reiser4 bits and he recommended I upgrade to
> > > 1.0.5.
> > >
> > > Are the 1.0.4 > 1.0.5 changes likely to be backported by SuSE into
> > > reiser4progs-1.0.4-2 and updated packages released? Should I be filing
> > > a bug on this somewhere, or will the SuSE people already know about
> > > this? Can anyone confirm what version of Reiser4 tools is in the latest
> > > OpenSuSE 10.1alpha?
> > >
> > > I really don't want to get into building packages myself - the whole
> > > point of our evaluation is to test out Reiser4 for use on production
> > > machines and we're not going to be building Reiser4 ourselves for a
> > > production machine even if the performance is great :-)
> > >
> > > If OpenSuSE 10.1 has the 1.0.5 Reiser4 tools then I might as well
> > > upgrade the box to OpenSuSE 10.1 for our testing, even if it is still
> > > an alpha release.
> > >
> > > Thanks in advance for any advice,
> > >
> > > James
sorry!
On Wednesday 14 December 2005 08:40, kanenas@xxxxxxxxxxxxx wrote:
> Thanks, that did it. Actually I also disabled kwallet in the geneneral
> settings as well (the other tab besides access controls), have not seen
> anything adverse yet...
> d.
>
> On Wednesday 14 December 2005 07:05, Andrei Verovski (aka MacGuru) wrote:
> > Hi,
> >
> > Have you formatted your RAID volume as Reiser4 root? BTW, did you compile
> > Reiser4 support into SuSE kernel yourself?
> >
> > On Wednesday 14 December 2005 12:21, Sbs Bofh wrote:
> > > SuSE 10.0 ships with Reiser4 support as optional packages (
> > > reiser4progs-1.0.4-2 and libaal-1.0.4-2). I'm aware that Reiser4 is
> > > not in the stock kernel yet and that its inclusion seems to be a
> > > slightly contentious issue.
> > >
> > > ...however...
> > >
> > > on a test machine I've been putting Reiser4 through its paces. The box
> > > is AMD64-powered, boots from an IDE drive and has a 3ware RAID
> > > controller with 4x 300GB drives, as a RAID5 array w/ hot spare. The
> > > entire /dev/sda device was set up in to LVM2 and there's a 838GB
> > > Reiser4 filesystem on it.
> > >
> > > So far, so good. I've loaded hundreds of GB of data and set up a
> > > mailserver with Maildirs and I have to say the performance is
> > > impressive.
> > >
> > > EXCEPT, I get fairly regular corruption on the Reiser4 filesystem,
> > > which can only be fixed with a "fsck.reiser4 --build-fs" (although it
> > > does fix the corruption and I haven't yet found any evidence of lost
> > > data - lost+found is always empty).
> > >
> > > After contacting Vitaly Fertman at Namesys for assistance it appears
> > > that this is due to an issue with "plugin set fields" (his words) in
> > > the 1.0.4version of the Reiser4 bits and he recommended I upgrade to
> > > 1.0.5.
> > >
> > > Are the 1.0.4 > 1.0.5 changes likely to be backported by SuSE into
> > > reiser4progs-1.0.4-2 and updated packages released? Should I be filing
> > > a bug on this somewhere, or will the SuSE people already know about
> > > this? Can anyone confirm what version of Reiser4 tools is in the latest
> > > OpenSuSE 10.1alpha?
> > >
> > > I really don't want to get into building packages myself - the whole
> > > point of our evaluation is to test out Reiser4 for use on production
> > > machines and we're not going to be building Reiser4 ourselves for a
> > > production machine even if the performance is great :-)
> > >
> > > If OpenSuSE 10.1 has the 1.0.5 Reiser4 tools then I might as well
> > > upgrade the box to OpenSuSE 10.1 for our testing, even if it is still
> > > an alpha release.
> > >
> > > Thanks in advance for any advice,
> > >
> > > James
| < Previous | Next > |