Date: Wed, 8 Oct 2014 16:54:45 +0000 From: "Meyer, Conrad" <conrad.meyer@isilon.com> To: "Pokala, Ravi" <rpokala@panasas.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: RE: Seeking reviewers for patch; PR 193873 Message-ID: <A3CAF0E84A34A540B4C74454358E003F2E4EFDEB@MX103CL02.corp.emc.com> In-Reply-To: <D05943F7.11EE9C%rpokala@panasas.com> References: <D05943F7.11EE9C%rpokala@panasas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(Apologies for the top-post.) Hi Ravi, Please file a bug in bugzilla and assign it to me. Thanks, Conrad ________________________________________ From: owner-freebsd-hackers@freebsd.org [owner-freebsd-hackers@freebsd.org] on behalf of Pokala, Ravi [rpokala@panasas.com] Sent: Wednesday, October 08, 2014 7:42 AM To: freebsd-hackers@freebsd.org Subject: Re: Seeking reviewers for patch; PR 193873 Hi Conrad, As mentioned in another thread ([1], [2]), I'm looking at dumping on systems w/ AF-4Kn drives (on a fairly old version of FreeBSD). Unfortunately, I'm not at all familiar w/ the process. I'm going to pick at it a few more days, but will probably end up having to punt and dumpsys onto a 512n or AF-512e device. But, since you are refactoring all this code in -CURRENT anyway, I think it would be awesome if you could look to the future and make it work w/o assuming that dump device block size is DEV_BSIZE; it would be better to use the sector size, as returned (for example) by ioctl(DIOCGSECTORSIZE). That won't help me now, but hopefully it will help everyone in the future. Thanks, Ravi [1]: https://lists.freebsd.org/pipermail/freebsd-hackers/2014-September/046164.html [2]: https://lists.freebsd.org/pipermail/freebsd-hackers/2014-October/046181.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3CAF0E84A34A540B4C74454358E003F2E4EFDEB>