| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Recover a XFS on raid -1 (linear) when one disk is broken |
| From: | Jan Banan <b@xxxxxxxxxxxx> |
| Date: | Wed, 04 Aug 2004 15:34:55 +0200 |
| Cc: | Chris Wedgwood <cw@xxxxxxxx> |
| In-reply-to: | <20040731183312.GD11283@taniwha.stupidest.org> |
| References: | <40F6DBC1.6050909@grabbarna.nu> <20040715205910.GA9948@taniwha.stupidest.org> <40F9321C.7060403@grabbarna.nu> <20040717203943.GL20260@plato.local.lan> <410ADC0A.6060100@grabbarna.nu> <20040731054924.GA4748@taniwha.stupidest.org> <410B4BC3.8000404@grabbarna.nu> <20040731091220.GA6158@taniwha.stupidest.org> <410BE0A9.3030904@grabbarna.nu> <20040731183312.GD11283@taniwha.stupidest.org> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 |
According to the man-page of "dd" then "seek" and "skip" skips "ibs/obs-sized BLOCKS" and not "SECTORS". So am I typing the correct value (28117692)? There is one thing that seem strange to me. "fdisk -l /dev/hdh" (the damaged harddisk) says /dev/hdh1 1 30515 245111706 83 Linux But now "dd" is working with sectors above 245111706, how is that possible? Right now it seem to be at 244536664 according to /var/log/messages: Aug 4 15:32:56 d kernel: hdh: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Aug 4 15:32:56 d kernel: hdh: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=244536735, high=14, low=9655711, sector=244536672
Aug 4 15:32:56 d kernel: end_request: I/O error, dev 22:41 (hdh),
sector 244536672Best regards, Jan rom owner-linux-xfs Wed Aug 4 06:55:41 2004 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Aug 2004 06:55:49 -0700 (PDT) Received: from mail.dfi-intl.com (w0user.dfi-intl.com [63.174.101.50] (may be forged)) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id i74Dtew4009295 for <linux-xfs@xxxxxxxxxxx>; Wed, 4 Aug 2004 06:55:40 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: XFS vs. EXT3 - Performance Questions. Date: Wed, 4 Aug 2004 09:55:31 -0400 Message-ID: <C1A9E874578A50438DE7C426DC626B88EF3D24@xxxxxxxxxxxxxxxxxxxxxxxxx> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XFS vs. EXT3 - Performance Questions. Thread-Index: AcR6KrSyVE/qDPwQTzyG+Ds1QyVGBQ== From: "Errol Neal" <eneal@xxxxxxxxxxxx> To: <linux-xfs@xxxxxxxxxxx> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id i74Dtfw4009296 X-archive-position: 3831 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@xxxxxxxxxxx Errors-to: linux-xfs-bounce@xxxxxxxxxxx X-original-sender: eneal@xxxxxxxxxxxx Precedence: bulk X-list: linux-xfs Hello folks. I am trying to determine if XFS offers any performance advantages over EXT3 for our environment. I've been doing some testing between the two using a Power Edge 1650 with 1GB Ram, 2 X 1.4 PIII CPUs and a single 36 GB disk. In my silly little "which file system can untar a kernel tar file the fastest", ext3 has always been faster, I mean significantly. Can anyone help me understand when one would want to use XFS over the default linux FS. Thanks in advance. Errol __________________________________________ Errol Uriel Neal Jr. Network Administrator DFI International, Inc. 1717 Pennsylvania Ave NW, Suite 1300 Washington, DC 20006 Tel (202)452-6955 Fax (202)452-6910 eneal@xxxxxxxxxxxx www.dfi-intl.com |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | ACL-over-XFS patch for 2.4.26 kernels?, Claude-Jacques Tronquet |
|---|---|
| Next by Date: | [Bug 272] xfs_force_shutdown in xfs_trans_cancel, part 2, bugzilla-daemon |
| Previous by Thread: | ACL-over-XFS patch for 2.4.26 kernels?, Claude-Jacques Tronquet |
| Next by Thread: | Re: Irreparable 'corrupt dinode ... error 990' Revisited, Federico Sevilla III |
| Indexes: | [Date] [Thread] [Top] [All Lists] |