graid3 device gives "Invalid argument" when requested to read>=128kb

[Vasil Dimov]

On Sat, Dec 30, 2006 at 04:39:39AM -0800, R. B. Riddick wrote:
> --- Ivan Voras <ivoras at fer.hr> wrote:
> > No, probably not. The whole thing was my very first attempt at doing
> > anything with GEOM (ggcomp - it still exists somewhere), which wasn't
> > very usable  :)  "Normal" file system operations worked, though I think
> > there were problems even here with 16 KB sectors.
> >
> Sector size seems to be not the reason (at least with gnop and dd on R6.1):
> 
> neo# gnop create -S 16384 md0
> neo# dd if=/dev/md0.nop of=/dev/null 
> dd: /dev/md0.nop: Invalid argument
> 0+0 records in
> 0+0 records out
> 0 bytes transferred in 0.000155 secs (0 bytes/sec)

This is because default dd's read block size is 512b

> neo# dd if=/dev/md0.nop of=/dev/null bs=16k
> 1024+0 records in
> 1024+0 records out
> 16777216 bytes transferred in 0.398660 secs (42084027 bytes/sec)
> 
> Just UFS seems to have a problem:
> 
> neo# newfs /dev/md0.nop
> /dev/md0.nop: 16.0MB (32768 sectors) block size 16384, fragment size 16384
>         using 4 cylinder groups of 4.02MB, 257 blks, 128 inodes.
> newfs: can't read old UFS1 superblock: read error from block device: Invalid
> argument

Look at newfs's -S switch, this is the same issue as with dd above.

-- 
Vasil Dimov
gro.DSBeerF at dv