Date: Tue, 10 Dec 2013 23:56:36 -0800 From: "ETHAN HOUSE (RIT Student)" <ewh2048@rit.edu> To: Erich Dollansky <erichsfreebsdlist@alogt.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Base System Rebuild Message-ID: <CAFRryZi65KHW70KZ%2BBRu6h8SUSoyGyq7jbF%2Bkt83uCPbHvk9mg@mail.gmail.com> In-Reply-To: <20131211152528.4978bd2b@X220.alogt.com> References: <CAFRryZg9GwSWLB3ytdpmVgrfnp4T0i6b0sgCJh9xuEdOic-Dng@mail.gmail.com> <20131210172513.77fa8482@X220.alogt.com> <CAFRryZivwj-0%2BSPO4gUZxv=0LAQZE8UoUrBOAb0cYVMZkUohtw@mail.gmail.com> <CAHu1Y72sTOpWSD_%2BKVwHxxj6N=L7aQdso092sYS=yeABFv=zXg@mail.gmail.com> <52A79136.7090103@ShaneWare.Biz> <76E49CC4-57CE-4A45-B051-025D465B311F@fisglobal.com> <CAFRryZjJ_Q2GGyPnAEKp_403f_8zOuG4FD%2BNdWCSJb%2BuvBgQ0w@mail.gmail.com> <20131211115641.5e15206e@X220.alogt.com> <CAFRryZghKK55kFUbnzKC7omkNCkqeJ7-Kg76QWBsZ=jeA5sGbA@mail.gmail.com> <20131211134031.77ef3e84@X220.alogt.com> <CAFRryZi0coRx%2B3urhvj=jvAKfhdc3=YkhbpcLs4mdKVN%2B3buCA@mail.gmail.com> <20131211140921.27cf6249@X220.alogt.com> <CAFRryZj6n8NuT1AViCkQLWyjGUG6HDM_vyzcMYTryHnhf5tT0Q@mail.gmail.com> <20131211144403.711eb6a9@X220.alogt.com> <CAFRryZjAvexmHGS8%2Bm6v=61oYGcag55wba%2BgzaB0afArhmLcMw@mail.gmail.com> <20131211150001.75bb1a1a@X220.alogt.com> <CAFRryZgy5e0CyqEQnOud8ewDmVi700i=64dUb0P=V-nyCBRS5Q@mail.gmail.com> <20131211152528.4978bd2b@X220.alogt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have access to both the Host and the VM. Due to my distance and horrifying internet connection interacting with libvirt and virtmanager is a nightmare. Lessons have been learned. Ethan House On Tue, Dec 10, 2013 at 11:25 PM, Erich Dollansky < erichsfreebsdlist@alogt.com> wrote: > Hi, > > On Tue, 10 Dec 2013 23:07:54 -0800 > "ETHAN HOUSE (RIT Student)" <ewh2048@rit.edu> wrote: > > > The VMHost is on a journaled file system so that shouldn't happen. > > It's also on a UPS. > > > so, to what do you have access? To the host or to the virtual machine > inside? > > You should never get affected by any file system problems of the host > except that your imagine will crash. > > > It was setup on a single partition, so newfs is not possible. > > You learned now the hard way that it is better to have several > partitions. A system with partitions for /, swap, /tmp, /var, /usr and > home has a much higher chance to avoid the problem you got caught in. > Of course, setting it up takes a bit more time. > > Erich > > > > Ethan House > > > > > > On Tue, Dec 10, 2013 at 11:00 PM, Erich Dollansky < > > erichsfreebsdlist@alogt.com> wrote: > > > > > Hi, > > > > > > On Tue, 10 Dec 2013 22:46:52 -0800 > > > "ETHAN HOUSE (RIT Student)" <ewh2048@rit.edu> wrote: > > > > > > > It was a VM. > > > > > > you mean that it is? > > > > > > > > Problem is the person who set up this machine had never used > > > > FreeBSD before and made a lot of really weird mistakes. I think > > > > the best course of action is to just create a new VM image and > > > > start from scratch. > > > > > > But damaging the file system should have nothing to do with it. > > > With an UPS, the file system only gets damages when the kernel > > > crashes with open writes. > > > > > > If possible, I would not install a new image but try to do a newfs > > > on as many partitions as possible. If the machine is setup with the > > > new approach of having only one partition, this is not possible. > > > > > > Erich > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFRryZi65KHW70KZ%2BBRu6h8SUSoyGyq7jbF%2Bkt83uCPbHvk9mg>