On Mon, 2007-10-29 at 10:31 +0000, Anton Altaparmakov wrote: > Could you post the complete dmesg output, please? Attached. This is after a reboot though, but a fresh attempt to sum the 0 length file, so the NTFS message is there. > Nothing related has changed in the NTFS driver between 2.6.22.10 and > 2.6.23 so I expect something else to be at fault here. > > Could you post your .config as well, please? Also attached. -Mike
Attachment:
dmesg.gz
Description: GNU Zip compressed data
Attachment:
config.gz
Description: GNU Zip compressed data
- Follow-Ups:
- Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D state hang
- From: Anton Altaparmakov <[email protected]>
- Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D state hang
- References:
- 2.6.23 regression: second access of empty ntfs file leads to D state hang
- From: Mike Galbraith <[email protected]>
- Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D state hang
- From: Anton Altaparmakov <[email protected]>
- 2.6.23 regression: second access of empty ntfs file leads to D state hang
- Prev by Date: Re: development package for the kernel log daemon
- Next by Date: Re: Device mapper regression 2.6.23 vs. v2.6.23-6597-gcfa76f0
- Previous by thread: Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D state hang
- Next by thread: Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D state hang
- Index(es):
 |