| To: | Dirk Munzinger <Dirk.Munzinger@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs-filesystem is broken after rsync |
| From: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> |
| Date: | Wed, 31 Jul 2002 14:49:00 +0200 |
| >received: | from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 81FEA57306; Wed, 31 Jul 2002 14:49:01 +0200 (CEST) |
| Cc: | Seth Mos <knuffie@xxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| Organization: | Sauter AG, Basel |
| References: | <3D46A2E4.8050106@sem-gmbh.com> <1028040131.2511.1.camel@stout.americas.sgi.com> <4.3.2.7.2.20020731105914.0335e828@pop.xs4all.nl> <3D47ADB9.20501@sem-gmbh.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Dirk Munzinger schrieb: > > Moin, > > Seth Mos schrieb: > > > > Can you give me a overview of the hardware this is running on? Can you > > also list what other patches are applied to this kernel beside the ipsec > > patches? > > The hardware is an AMD K6 2/450 with 256 MB and 3 IDE HDs from IBM (it's > just a backup server for the online-backup) > In the meantime I have recompiled the 2.4.18 kernel only with the ipsec > and the xfs patches - no other patches anymore. > > I am now testing with ext3. Formating the fs with mkfs.ext3 -c showed no > problems. Thats only read test, did you try, when formatted XFS, to fill the partition so any write error on the disks can show up? Also, did you check your memory? Since XFS sometimes consumes much more memory than with other filesystems, memory errors can show up, memtest86 is your friend. Simon > > Regards, Dirk |
| Previous by Date: | Re: xfs-filesystem is broken after rsync, Dirk Munzinger |
|---|---|
| Next by Date: | Re: XFS stack overflow, Steve Lord |
| Previous by Thread: | Re: xfs-filesystem is broken after rsync, Seth Mos |
| Next by Thread: | xfs-filesystem is broken after rsync (log-info), Dirk Munzinger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |