All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Christian Fritze <The.Finn@sprawl.de>
Cc: reiserfs-list@namesys.com
Subject: Re: FAQ 29 says to put 0s into /etc/fstab -- What if I don't?
Date: Mon, 24 Mar 2003 12:23:27 +0300	[thread overview]
Message-ID: <20030324122327.A7544@namesys.com> (raw)
In-Reply-To: <200303240910.KAA02175@chatsubo.sprawl.de>

Hello!

On Mon, Mar 24, 2003 at 10:10:50AM +0100, Christian Fritze wrote:

> Doing forensics...
> A customer has leased a low budget server for a couple of small projects. 
> Recently the disk in that machine failed and was replaced. The provider's
> technician who did the replacement and the initial setup (up to a running
> sshd where I take over such a machine) installed reiserfs systems on the
> partitions that (on the old disk) had carried ext3. However he did *not*
> tell me about the change *and* he put '1 1' and '1 2' resp. into fstab as
> he usually does whith ext3 filesystems. And yes: I did not check in due
> time, trusting in work done by others... :-(

This is nothing to fear.
reiserfsck will be sturted on each boot, and it will immediately terminate once
it discovers it was called during boot process.

> Last weekend that machine rebooted (for no apparent reason, I'm beginning
> to feel annoyed about that provider...) the first time after the hardware
> replacement. Hours later my customer tells me that something seems to be 
> wrong. I look at the machine and the partition that carries project data
> seems to be completely empty, not a single file or directory, nothing!

Hm, any chance that it was not mounted and you are looking at non-mounted directory?

> After a first moment of horror thinking came back, I checked a few things
> and came across those unexpected reiserfs lines in fstab. Then I read the 
> FAQ and finally daring a 'reiserfsck --rebuild-tree' brought me back to 
> normal life.

Hm. Was there anything strange in logs prior to/immediately after unexpected reboot?

> Is this behaviour to be expected when putting the wrong things into fstab? 

No.

> (In this case the FAQ could probably talk a bit 'louder' about it... ;-)
> Or should I still search for other reasons as well? I had no time yet to

Yes, you should.

> build a nice kernel after the disk failure and maybe running the standard 
> SuSE 2.4.19 as installed from DVD isn't such a good idea in the first place?

They had lots of updates since then, I think. You might want to pick up those.

Bye,
    Oleg

      reply	other threads:[~2003-03-24  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24  9:10 FAQ 29 says to put 0s into /etc/fstab -- What if I don't? Christian Fritze
2003-03-24  9:23 ` Oleg Drokin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030324122327.A7544@namesys.com \
    --to=green@namesys.com \
    --cc=The.Finn@sprawl.de \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.