Date: Fri, 31 Jan 2003 16:44:07 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Julian Elischer <julian@elischer.org> Cc: Steve Byan <stephen_byan@maxtor.com>, freebsd-fs@FreeBSD.ORG, tech-kern@netbsd.org Subject: Re: DEV_B_SIZE Message-ID: <3E3B1857.2122B84F@mindspring.com> References: <Pine.BSF.4.21.0301311002110.45015-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > I presume that if such a drive were made, thre would be some way to > identify it? > > It would be very easy to configure a filesystem to have a minimum > writable unit size of 4k, and I assume that doing so would be > slightly advantageous. (no Read/modify/write). it would however > be good if we could easily identify when doing so was a good idea. Substantial modifications would be required to the UFS directory management code to support both old and new disks in the same machine with the same FS code. Assuming that was addressed by making the DEVBSIZE define into a variable based on the underlying device, there's the problem of device concatenation. Your devices would have to be made up of homogeneous components, too, so once you got them to coexist with old disks, you would still not be able to get them to aggregate with them, in, e.g., a RAID 0, and maybe not in any RAID set. > I'd say that this means that the drive should hold the active 4k block > in nvram or something.. This would be very useful, but unlikely in the extreme, I think, because of the associated costs. 8-(. But it would be very, very useful. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E3B1857.2122B84F>