Date: Wed, 25 Jul 2007 01:01:28 -0500 From: "illoai@gmail.com" <illoai@gmail.com> To: "Zbigniew Szalbot" <zbigniew@szalbot.homedns.org> Cc: Freebsd questions <freebsd-questions@freebsd.org> Subject: Re: fsck to fix HD problem Message-ID: <d7195cff0707242301q402d06ecjddc82db368ddf205@mail.gmail.com> In-Reply-To: <460a65190bb88ed0676417e1033dd160@szalbot.homedns.org> References: <d7195cff0707242244q3263040dy1267a40b1be0437f@mail.gmail.com> <460a65190bb88ed0676417e1033dd160@szalbot.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/07/07, Zbigniew Szalbot <zbigniew@szalbot.homedns.org> wrote: > > Hello, > > >> so I decided to use fsck to check my HD. I ran it > >> in the foreground mode with the -y flag. It gives me the below > >> information. My question is - should I worry (it is more a home machine > >> than a real server) and if yes, how can I fix the problem? > > . . . > > > > To do anything more than merely report problems > > you should drop into single-user mode, unmount > > everything except root (hopefully. If it gets angry, > > reboot into single-user mode.) and run fsck (as is > > or with the -y flag if you feel daring.) on the filesystems > > in question. > > Is the single-user mode necessary. As it is a family machine I know when I > am the only one using it. > Well, fsck-ing /var on a fully multiuser system is hairy, at best, since /var is almost always being written to by something or other. Single user mode is the simplest way of dealing with this, since none of the logging, mail, or one of any of a 10^4 daemons will be trying to write to it, while you're trying to fix it. With mysql, I would assume* many of the same problems with /usr (or /usr/local, if that is its own filesystem). *given that I know meow-all about mysql: where it may wish to write, or what horrible perversions it commits while running. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0707242301q402d06ecjddc82db368ddf205>