Date: Thu, 9 Apr 2009 11:43:11 +0100 From: Chris Rees <utisoft@googlemail.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Dump/Restore Message-ID: <b79ecaef0904090343i32822b51r3f2fafc141189195@mail.gmail.com> In-Reply-To: <b79ecaef0904090342x453953a0l4800967500b1bbcd@mail.gmail.com> References: <E8298C3B2FC1CC43B3FBAC70544780A602D45103@EXCH-01.mbint.multibanka.com> <b79ecaef0904090155h48b2b707h5576dd21dad5cea3@mail.gmail.com> <E8298C3B2FC1CC43B3FBAC70544780A602D45105@EXCH-01.mbint.multibanka.com> <b79ecaef0904090342x453953a0l4800967500b1bbcd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/4/9 Daniels Vanags <daniels.vanags@smpbank.lv>: > This is a source comp output, after dump/restore /dev is empty. I run fre= esbie on target machine. > > -----Original Message----- > From: Chris Rees [mailto:utisoft@googlemail.com] > Sent: Thursday, April 09, 2009 11:56 AM > To: Daniels Vanags > Subject: Re: Dump/Restore > > 2009/4/9 Daniels Vanags <daniels.vanags@smpbank.lv>: >> Please Help! After dump-restore /dev, /proc, /usr/compat/linux/proc - is >> empty, system fealure to boot. Please guide me, how to dump/restore >> devfs. >> >> >> >>> df -h >> >> Filesystem =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Size =A0 =A0Used =A0 = Avail Capacity =A0Mounted on >> >> /dev/mirror/gm0s1a =A0 =A0 =A0 =A0 52G =A0 =A0 37G =A0 =A0 11G =A0 =A078= % =A0 =A0/ >> >> devfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.0K =A0 = =A01.0K =A0 =A0 =A00B =A0 100% =A0 =A0/dev >> >> procfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.0K =A0 =A04= .0K =A0 =A0 =A00B =A0 100% =A0 =A0/proc >> >> linprocfs =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.0K =A0 =A04.0= K =A0 =A0 =A00B =A0 100% >> /usr/compat/linux/proc >> > > But.... /proc, /dev, and /u/c/l/proc are full in that df output... > What are you talking about? Try ls /dev, and post that. Pretty sure it > should be normal. > > > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > You need to check then, that /dev is mounted. # mount -t devfs devfs /dev Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b79ecaef0904090343i32822b51r3f2fafc141189195>