public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Nekrasov <andy@spylog.ru>
To: linux-kernel@vger.kernel.org
Subject: aic7xxx & software raid5 & 2.4.20pre2 (Happened terrible)
Date: Mon, 26 Aug 2002 09:42:33 +0400	[thread overview]
Message-ID: <20020826054233.GA12073@an.local> (raw)

Hello.


1. kernel 2.4.20pre2
   hardware Intel LanceWood L440GX with onboard AIC controller
   4 hdd, "Vendor: IBM       Model: DDYS-T18350M      Rev: S93E
 
2. software raid5:

 Personalities : [raid1] [raid5] [multipath] 
 read_ahead 1024 sectors
 md0 : active raid5 sdd2[3] sdc2[2] sdb2[1] sda2[0]
       52146624 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      
 unused devices: <none>

3. log:

...
Aug 21 16:37:29 ruby kernel: 09:00: rw=0, want=140379796, limit=52146624
Aug 21 16:37:29 ruby kernel: attempt to access beyond end of device
Aug 21 16:37:29 ruby kernel: 09:00: rw=0, want=1938395668, limit=52146624
Aug 21 16:37:29 ruby kernel: attempt to access beyond end of device
Aug 21 16:37:29 ruby kernel: 09:00: rw=0, want=1971900992, limit=52146624
Aug 21 16:37:29 ruby kernel: attempt to access beyond end of device
Aug 21 16:37:29 ruby kernel: 09:00: rw=0, want=1971900992, limit=52146624
Aug 21 16:37:29 ruby kernel: attempt to access beyond end of device
Aug 21 16:37:29 ruby kernel: 09:00: rw=0, want=140379796, limit=52146624
Aug 24 16:30:49 ruby kernel: attempt to access beyond end of device
Aug 24 16:30:49 ruby kernel: 09:00: rw=0, want=140379796, limit=52146624
Aug 24 16:30:49 ruby kernel: attempt to access beyond end of device
Aug 24 16:30:49 ruby kernel: 09:00: rw=0, want=1938395668, limit=52146624
Aug 24 16:30:49 ruby kernel: attempt to access beyond end of device
Aug 24 16:30:49 ruby kernel: 09:00: rw=0, want=1971900992, limit=52146624
Aug 24 16:30:49 ruby kernel: attempt to access beyond end of device
Aug 24 16:30:49 ruby kernel: 09:00: rw=0, want=1971900992, limit=52146624
Aug 24 16:30:49 ruby kernel: attempt to access beyond end of device
Aug 24 16:30:49 ruby kernel: 09:00: rw=0, want=140379796, limit=52146624
...

4. after uptime 8 day /dev/md0 - go "read-only"
   (tune2fs enable on /dv/md0 "Errors behavior:Remount read-only")
   and e2fsck found many error (empty lost+found)


Question: why such can occur and what to make to avoid repetition?

-- 
bye.
Andrey Nekrasov, SpyLOG.

                 reply	other threads:[~2002-08-26  5:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020826054233.GA12073@an.local \
    --to=andy@spylog.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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