Re: 64-bit block sizes on 32-bit systems

From: Matthew Wilcox (matthew@wil.cx)
Date: Mon Mar 26 2001 - 13:07:33 EST

Next message: Tim Waugh: "Re: paride error, aparantly with VFS"
Previous message: Greg KH: "2.2.19 toshiba module fix"
In reply to: Manfred Spraul: "Re: 64-bit block sizes on 32-bit systems"
Next in thread: LA Walsh: "Re: 64-bit block sizes on 32-bit systems"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Mar 26, 2001 at 08:01:21PM +0200, Manfred Spraul wrote:
> drivers/block/ll_rw_blk.c, in submit_bh()
> > bh->b_rsector = bh->b_blocknr * (bh->b_size >> 9);
>
> But it shouldn't cause data corruptions:
> It was discussed a few months ago, and iirc LVM refuses to create too
> large volumes.

Ah yes, I'd forgotten the block layer still works in terms of 512-byte blocks.

-- 
Revolutions do not require corporate support.
-
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 message: Tim Waugh: "Re: paride error, aparantly with VFS"
Previous message: Greg KH: "2.2.19 toshiba module fix"
In reply to: Manfred Spraul: "Re: 64-bit block sizes on 32-bit systems"
Next in thread: LA Walsh: "Re: 64-bit block sizes on 32-bit systems"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Mar 31 2001 - 21:00:14 EST