On Thu, Sep 18, 2008 at 3:43 AM, Jeremy Katz [EMAIL PROTECTED] wrote:
How often are you actually getting to having fsck questions?
Hi Jeremy,
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in
hi Joshua,
Just to clarify:
Most of them
will be in locations with unreliable power - so they will switch off
when power gets cut.
I have run servers like this for a few years with ext3. I was surprised
how well it worked. I never got anything resembling file system
corruption. ext3
On Thu, Sep 18, 2008 at 3:43 AM, Jeremy Katz [EMAIL PROTECTED] wrote:
How often are you actually getting to having fsck questions?
Hi Jeremy,
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in
On Thu, Sep 18, 2008 at 12:49:22PM +1200, Martin Langhoff wrote:
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in locations with unreliable power - so they will switch off
when power gets
On Thu, Sep 18, 2008 at 12:49:22PM +1200, Martin Langhoff wrote:
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in locations with unreliable power - so they will switch off
when power gets
On Thu, Sep 18, 2008 at 1:46 PM, Joshua N Pritikin [EMAIL PROTECTED] wrote:
I have run servers like this for a few years with ext3. I was surprised
how well it worked. I never got anything resembling file system
corruption. ext3 worked like a charm.
Good to hear!
What tended to fail was the
hi,
The xs-config package creates a file called /fsckoptions (yes, in /),
to stop headless servers from stalling on fsck questions.
This file is deleted by anaconda, some time after the end of ks.cfg's
%post section. To be sure, I used:
%post
#[...]
if [ -e /fsckoptions ]; then
touch
