summaryrefslogtreecommitdiffstats
path: root/sbin/dumpon
diff options
context:
space:
mode:
authormckusick <mckusick@FreeBSD.org>2003-05-07 18:27:09 +0000
committermckusick <mckusick@FreeBSD.org>2003-05-07 18:27:09 +0000
commit2e1c393dfc9eb11b05e093718baa11cd6a695a7d (patch)
treea7524c265464698a3f6530ac94f5bfd5c18248e7 /sbin/dumpon
parent1d8f58ae39f8fac245c251478decd0c1cae5c402 (diff)
downloadFreeBSD-src-2e1c393dfc9eb11b05e093718baa11cd6a695a7d.zip
FreeBSD-src-2e1c393dfc9eb11b05e093718baa11cd6a695a7d.tar.gz
Dump is hard-wired to believe that it can read disks on
1024-byte boundaries. For many years this was a reasonable assumption. However, in recent years we have begun seeing devices with 2048-byte sectors. These devices return errors when dump tries to read starting in the middle of a sector or when it tries to read only the first half of a sector. Rather than change the native block size used by dump (and thus create an incompatible dump format), this fix checks for transfer requests that start and/or end on a non-sector boundary. When such a read is detected, the new code reads the entire sector and copies out just the part that dump needs. Reviewed by: Poul-Henning Kamp <phk@critter.freebsd.dk> Approved by: re (John Baldwin <jhb@FreeBSD.org>) Sponsored by: DARPA & NAI Labs.
Diffstat (limited to 'sbin/dumpon')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud