In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Thu, 2 Jan 2003 [EMAIL PROTECTED] wrote: > >> In message <[EMAIL PROTECTED]>, Bruce Evans writes: >> > >> >The md driver doesn't set any of the si_ size parameters so it has no chance >> >of getting this stuff right when the parameters are not the defaults. >> >> It does however set its sectorsize to 4k. The problem was GEOM not >> setting si_bsize_phys on the dev_t. > >The problem must be deeper, since setting it in GEOM doesn't affect >the non-GEOM case. GEOM can't set it, since it might be different >from the sector size. Stefan Esser reported some ordering and/or >cloning problems. GEOM apparently creates an extra device whose >si_bsize_phys can't be touched by the md driver.
GEOM does not operate with two different sizes, it operates with a sectorsize which is defined as the smallest size of data the unit supports. Transferring this from md to GEOM to the dev_t should solve the problem in the GEOM case. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
