From: Mike Galbraith <efault@gmx.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D state hang
Date: Mon, 29 Oct 2007 15:43:17 +0100 [thread overview]
Message-ID: <1193668997.7284.2.camel@Homer.simpson.net> (raw)
In-Reply-To: <4E61D235-B8E8-43DF-96A5-B3169E6AB223@cam.ac.uk>
On Mon, 2007-10-29 at 13:39 +0000, Anton Altaparmakov wrote:
> Hi Mike,
>
> Thanks for the files. That is really odd. And you are sure this just
> works with 2.6.22.10 on the exact same file? Have you run "chkdsk /
> f /v /x" on the NTFS volume from Windows?
Yes, 2.6.22.10 can md5sum that file just fine, did it several times. I
haven't run chkdsk.
> Would you be able to apply the attached patch to your 2.6.23.1 kernel
> and try again and then send me the NTFS error messages? The patch
> should cause more verbose error reporting to happen... Thanks!
[ 249.009250] NTFS-fs error (device hda1): ntfs_map_runlist_nolock(): vcn 0x0 >= end_vcn 0x0 for inode 0x490f, error 0.
[ 249.020142] NTFS-fs error (device hda1): ntfs_read_compressed_block(): ntfs_map_runlist() failed. Cannot read compression block.
-Mike
next prev parent reply other threads:[~2007-10-29 14:43 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
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 [this message]
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=1193668997.7284.2.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®