public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mateusz Berezecki <mateuszb@gmail.com>
To: Arnaud Boulan <arnaud.boulan@libertysurf.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs problem after usb hard drive disconnected
Date: Fri, 23 Sep 2005 23:40:57 +0200	[thread overview]
Message-ID: <20050923214057.GA15047@pc2> (raw)
In-Reply-To: <200509232121.52803.arnaud.boulan@libertysurf.fr>

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

Arnaud Boulan <arnaud.boulan@libertysurf.fr> wrote:
| Hello,
| 
| I am using an external USB hard drive, and i hit a bug in the reiserfs code 
| after the drive got disconnected by a power problem. You can see this in the 
| attached logs.
| The disconnection of the hard drive was not done manually, it has been 
| offlined "spontaneously" by what seems to be a power loss. In fact, i suspect 
| i have bad power at home since i have had other similar problems with another 
| device (an usb tv tuner)
| 
| However, i already have disconnected my drive manually a few times by mistake,
| and i always recovered from that by unmouting, running reiserfsck and 
| remounting the device.
| 
| This time, although i can consider it is a hardware problem, it would have 
| been nice if the kernel had also recovered from the USB problem. Instead, i 
| couldn't unmount the filesystem and the usb stack was stucked, leaving no 
| choice but to reboot...
| 

   Same problem here. Power went down and I had no other choice than to
   reboot. FS(ext3) got recovered almost completely but some page
   writes were lost. I were unable to unmount the disk too. I guess this
   is more a usb storage problem than a fs one (?) 


Sep 22 09:57:46 pc2 kernel: scsi0 (0:0): rejecting I/O to dead device
Sep 22 09:57:46 pc2 kernel: Buffer I/O error on device sda1, logical
block 24884044
Sep 22 09:57:46 pc2 kernel: lost page write due to I/O error on sda1
Sep 22 09:57:46 pc2 kernel: scsi0 (0:0): rejecting I/O to dead device
Sep 22 09:57:46 pc2 kernel: journal_bmap: journal block not found at
offset 3144 on sda1
Sep 22 09:57:46 pc2 kernel: Aborting journal on device sda1.
Sep 22 09:57:46 pc2 kernel: scsi0 (0:0): rejecting I/O to dead device
Sep 22 09:57:46 pc2 kernel: Buffer I/O error on device sda1, logical
block 527
Sep 22 09:57:46 pc2 kernel: lost page write due to I/O error on sda1
Sep 22 09:58:13 pc2 kernel: ext3_abort called.
Sep 22 09:58:13 pc2 kernel: EXT3-fs error (device sda1):
ext3_journal_start_sb: Detected aborted journal
Sep 22 09:58:13 pc2 kernel: Remounting filesystem read-only


 Mateusz

-- 
  @..@   Mateusz Berezecki 
 (----)  mateuszb@gmail.com http://mateusz.agrest.org
( >__< ) PGP: 5F1C 86DF 89DB BFE9 899E 8CBE EB60 B7A7 43F9 5808 
^^ ~~ ^^

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

      reply	other threads:[~2005-09-23 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23 19:21 reiserfs problem after usb hard drive disconnected Arnaud Boulan
2005-09-23 21:40 ` Mateusz Berezecki [this message]

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=20050923214057.GA15047@pc2 \
    --to=mateuszb@gmail.com \
    --cc=arnaud.boulan@libertysurf.fr \
    --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