Date: Wed, 12 Nov 2008 06:53:54 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Varshavchick Alexander <alex@metrocom.ru> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD 5.4 - filesystem full Message-ID: <20081112145354.GA27790@icarus.home.lan> In-Reply-To: <20081112172228.B65116@comanche.metrocom.ru> References: <20081112153331.K65116@comanche.metrocom.ru> <20081112124514.GA25369@icarus.home.lan> <20081112172228.B65116@comanche.metrocom.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 12, 2008 at 05:26:58PM +0300, Varshavchick Alexander wrote: >> I would start by taking the machine down, booting it into single-user, >> and running fsck -y. background fsck does not catch all errors. > > Okay then, are there any ways of performing it remotely, without my going > to the data center and standing near the server for an hour while it > checks? I mean are there any civil ways, or only running reboot -qn and > praying? :) Booting into single-user via serial console, KVM, KVM-over-IP, or iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are remote and you lack any of these features, I'm both surprised and not sure what to tell you. You'll encounter this problem with any OS, not just FreeBSD. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081112145354.GA27790>