On 2004.02.12 23:34, Andrew Morton wrote: > Nathan Scott <nathans@sgi.com> wrote: > > > > > This forces the underlying device(s) to a soft blocksize of 512. And > > > I had my 80 MB/sec write speed back ! > > > > > > I'm not sure if setting the blocksize of the underlying device > > > always to 512 is the right solution. I think that set_blocksize > > > > Hmm... that set_blocksize there must be new in -mm, I don't see > > that in mainline yet. I would guess that bdev_hardsect_size() > > would be more appropriate here than hard-coding 512 bytes. I > > don't know the details of the problem being solving by adding > > set_blocksize() in there though, so I might be completely wrong. > > Yes, 2.6.3-rc2-mm1 has a new device-mapper update. > > Miquel, thanks for picking this up. I shall wait for the LVM team to > suggest the preferred fix. Nah, forget about it. I don't think this actually matters, it's still something with the 3ware driver in RAID5 mode that fsckes this up. It needs more investigation (it seems there's some heisenberg effect in there, or I need more sleep). Mike. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
