[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071115135332.5a007334.akpm@linux-foundation.org>
Date: Thu, 15 Nov 2007 13:53:32 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jiri Kosina <jikos@...os.cz>
Cc: greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-rc2-mm1
On Thu, 15 Nov 2007 22:41:41 +0100 (CET)
Jiri Kosina <jikos@...os.cz> wrote:
> On Thu, 15 Nov 2007, Greg KH wrote:
>
> > This patch, as found by Dave Young, should fix the issue: I'll roll it
> > into my larger patchset so that Andrew will get it automatically next
> > release, but here it is for people to use now.
>
> Hmm, something strange going on here. With this patch applied on top of
> 2.6.24-rc2-mm1, I can't see no lockup or warning from kobjects code, which
> is good. But this happens:
>
> ...
> Creating device nodes with udev
> resume device not found (ignoring)
> Waiting for device
> /dev/disk/by-id/scsi-SATA_HDS722516VLSA80_VN6D3ECDE5BD9D-part6 to appear:
> ok
> showconsole: Warning: the ioctl TIOCGDEV is not known by the kernel
> fsck 1.40.2 (12-Jul-2007)
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a
> /dev/disk/by-id/scsi-SATA_HDS722516VLSA80_VN6D3ECDE5BD9D-part6
> Error writing block 1542 (Attempt to write block from filesystem resulted
> in short write).
>
> /dev/disk/by-id/scsi-SATA_HDS722516VLSA80_VN6D3ECDE5BD9D-part6: UNEXPECTED
> INCONSISTENCY; RUN fsck MANUALLY.
> (i.e., without -a or -p options)
> Error writing block 1542 (Attempt to write block from filesystem resulted in short write).
Yup. Please apply the fix from
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc2/2.6.24-rc2-mm1/hot-fixes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists