public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andrew Morton <akpm@osdl.org>, Jiri Slaby <jirislaby@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	sct@redhat.com, adilger@clusterfs.com,
	linux-ext3@vger.kernel.org
Subject: Re: 2.6.18-mm2: ext3 BUG?
Date: Sun, 8 Oct 2006 09:14:33 +0200	[thread overview]
Message-ID: <20061008071433.GC30283@lug-owl.de> (raw)
In-Reply-To: <20061008063330.GA30283@lug-owl.de>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On Sun, 2006-10-08 08:33:30 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> Just to add, I've seen right this, too, on Debian's 2.6.17-2-686, with
> a 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE
> (rev 01) (8086:7111) PATA controller with a ST3300822A disk. That's
> healthy from smartmontool's point of view. The machine has 192MB RAM, an
> Intel P3 processor and is idle during daytime, busy with fetching
> backups at night. I'm using this filesystem with faubackup, lots of
> small files, lots of hard links and a number of large files.  Some of
> the posts below mention large files, too.  My impression would be that
> it happens when unlink()ing large files.  Oh, and it's a LV, not a
> direct partition.

Another thing to add:  I don't think this corruption is related to the
PIIX4 controller. For some days (when we put the machines that were
backed-up into production), we tried to work with an external USB HDD.
(The backup box is off-site and only has limited bandwidth, so the
idea was to move the USB HDD to the main site if we were on fire
there. We gave up this idea due to too small USB performance.)

However, I've seen this problem twice with the USB-attached disk, too.
It's the exact same disk, we just threw away the case.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                http://catb.org/~esr/faqs/smart-questions.html
the second  :

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-08  7:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 21:35 2.6.18-mm2: ext3 BUG? Jiri Slaby
2006-10-05 21:50 ` Andrew Morton
2006-10-05 23:17   ` Jiri Slaby
2006-10-06  0:14     ` Andrew Morton
2006-10-06  9:33       ` Jiri Kosina
2006-10-08  6:33       ` Jan-Benedict Glaw
2006-10-08  7:14         ` Jan-Benedict Glaw [this message]
2006-10-08  8:48         ` Jan-Benedict Glaw
2006-10-08  9:54           ` Jiri Slaby
2006-10-10  7:09         ` Jan-Benedict Glaw
2006-10-11 10:42           ` Jan Kara
2006-10-23  8:13             ` Jan-Benedict Glaw
2006-10-23 10:41               ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061008071433.GC30283@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-ext3@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox