From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12896] ext3 FS problem or harddisk problem?
Date: Wed, 25 Mar 2009 14:51:21 GMT [thread overview]
Message-ID: <200903251451.n2PEpLeN032051@demeter.kernel.org> (raw)
In-Reply-To: <bug-12896-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12896
Jan Kara <jack@suse.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jack@suse.cz
--- Comment #3 from Jan Kara <jack@suse.cz> 2009-03-25 14:51:20 ---
This seems like a problem with your USB drive (or motherboard having too weak
USB controller to power the drive or something like that). Because the drive
disconnects after being mounted and later also gives IO errors. See:
Mar 20 16:45:57 usb 1-6: configuration #1 chosen from 1 choice
Mar 20 16:45:57 localhost kernel: scsi9 : SCSI emulation for USB Mass Storage
devices
Mar 20 16:46:02 localhost kernel: scsi 9:0:0:0: Direct-Access WD
1600BEAExternal 1.02 PQ: 0 ANSI: 0
Mar 20 16:46:02 localhost kernel: sd 9:0:0:0: [sde] 312581808 512-byte hardware
sectors: (160 GB/149 GiB)
...
Mar 20 16:46:04 localhost kernel: EXT3 FS on sde1, internal journal
...
Mar 20 16:46:47 localhost kernel: usb 1-6: USB disconnect, address 4
...
Mar 20 16:47:00 localhost kernel: EXT3-fs error (device sde1):
ext3_get_inode_loc: unable to read inode block - inode=2, block=1027
Mar 20 16:47:00 localhost kernel: EXT3-fs error (device sde1) in
ext3_reserve_inode_write: IO failure
...
And there are more IO errors because the drive then reconnects, gets sdf
assigned but disconnects again. Anyway, this is either USB stack or HW problem.
If you see it only with some kernel and not with other, it might be worth
pursuing further. Otherwise I'd try to play with HW...
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-03-25 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 9:16 [Bug 12896] New: ext3 FS problem or harddisk problem? bugme-daemon
2009-03-20 11:21 ` [Bug 12896] " bugme-daemon
2009-03-22 23:37 ` bugme-daemon
2009-03-25 14:51 ` bugzilla-daemon [this message]
2009-03-25 15:33 ` bugzilla-daemon
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=200903251451.n2PEpLeN032051@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).