From: Mike Galbraith <efault@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23 regression: second access of empty ntfs file leads to D state hang
Date: Mon, 29 Oct 2007 07:18:01 +0100 [thread overview]
Message-ID: <1193638681.7409.22.camel@Homer.simpson.net> (raw)
In-Reply-To: <1193638086.7409.21.camel@Homer.simpson.net>
hrmph, CC to members only list removed.
On Mon, 2007-10-29 at 07:08 +0100, Mike Galbraith wrote:
> Greetings,
>
> I've stumbled across a 2.6.22->2.6.23 regression. First md5sum access
> of an empty NTFS file leads to kernel I/O error gripe, a second access
> leaves md5sum hung. 2.6.22.10 has no trouble accessing this file.
>
> Looking at the 22->23 diff, I don't see a quick and dirty stab
> candidate, and since I'm preparing for a 5 week separation from my box
> <twitch>, I doubt I'll have time to do a bisect. /me punts.
>
> root@Homer: md5sum '/windows/C/Dokumente und Einstellungen/All Users/Anwendungsdaten/Microsoft/Network/Connections/Pbk/rasphone.pbk'
> md5sum: /windows/C/Dokumente und Einstellungen/All Users/Anwendungsdaten/Microsoft/Network/Connections/Pbk/rasphone.pbk: Input/output error
>
> [ 228.551859] NTFS-fs error (device hda1): ntfs_read_compressed_block(): ntfs_map_runlist() failed. Cannot read compression block.
>
> [ 401.721890] md5sum D eee53d64 0 7249 7019
> [ 401.727155] eee53d78 00200082 00000002 eee53d64 eee53d5c 00000000 e9b006b0 e9b00700
> [ 401.735469] 5f6b3463 c0677060 c067a080 e9b00860 c180d080 00000000 c180d080 c180d108
> [ 401.743991] 00000001 00200086 e9b006e0 00200086 f79ca640 eee53d94 0000b4d3 00200202
> [ 401.752514] Call Trace:
> [ 401.755155] [<c04b57bf>] io_schedule+0x1e/0x28
> [ 401.759711] [<c015a269>] sync_page+0x34/0x3f
> [ 401.764102] [<c04b5b78>] __wait_on_bit_lock+0x40/0x63
> [ 401.769281] [<c015a221>] __lock_page+0x54/0x5c
> [ 401.773845] [<c015a826>] do_generic_mapping_read+0x236/0x4e7
> [ 401.779629] [<c015c165>] generic_file_aio_read+0xff/0x198
> [ 401.785138] [<c017851c>] do_sync_read+0xd0/0x106
> [ 401.789873] [<c0178cff>] vfs_read+0x89/0x11d
> [ 401.794266] [<c0179164>] sys_read+0x3d/0x64
> [ 401.798569] [<c01041ba>] syscall_call+0x7/0xb
> [ 401.803039] =======================
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-10-29 6:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 6:08 Mike Galbraith
2007-10-29 6:18 ` Mike Galbraith [this message]
2007-10-29 10:40 ` Anton Altaparmakov
2007-10-29 10:31 ` [Linux-NTFS-Dev] " Anton Altaparmakov
2007-10-29 11:45 ` Mike Galbraith
2007-10-29 13:39 ` Anton Altaparmakov
2007-10-29 13:41 ` Anton Altaparmakov
2007-10-29 14:43 ` Mike Galbraith
2007-10-29 15:18 ` Mike Galbraith
2007-10-30 8:00 ` Mike Galbraith
2007-10-30 9:23 ` Anton Altaparmakov
2007-11-02 19:22 ` Anton Altaparmakov
2007-11-03 4:56 ` Mike Galbraith
2007-11-03 7:27 ` Anton Altaparmakov
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=1193638681.7409.22.camel@Homer.simpson.net \
--to=efault@gmx.de \
--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
Powered by JetHome