On Fri, Nov 19, 2004 at 05:00:27PM -0800, Randy Bush
wrote:> RELENG_5 as of 2004.11.19 06:35 gmt
> but this has been happening on this box for a long while
>
> Mounting root from ufs:/dev/twed0s1a
> Pre-seeding PRNG: kickstart.
> Loading configuration files.
> Entropy harvesting: interrupts ethernet point_to_point kickstart.
> dumpon: /dev/twe0s1b: No such file or directory
> swapon: adding /dev/twed0s1b as swap device
> Starting file system checks:
> /dev/twed0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/twed0s1a: clean, 94526 free (790 frags, 11717 blocks, 0.6%
fragmentation)
> /dev/twed0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/twed0s1d: clean, 380798 free (1614 frags, 47398 blocks, 0.3%
fragmentation)
> /dev/twed0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/twed0s1e: clean, 425408 free (672 frags, 53092 blocks, 0.1%
fragmentation)
> /dev/twed0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/twed0s1f: clean, 6748076 free (61780 frags, 835787 blocks, 0.6%
fragmentation)
> /dev/twed0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/twed0s1g: clean, 16688179 free (39635 frags, 2081068 blocks, 0.2%
fragmentation)
> /dev/twed0s1h: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/twed0s1h: clean, 31547 free (67 frags, 3935 blocks, 0.2%
fragmentation)
>
> so why won't /dev/twe0s1b handle dumpon?
Because you want /dev/twed0s1b not /dev/twe0s1b. From the source it
appears that there is dump support.
-- brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20041119/c4926ebc/attachment.bin