Well, the good news is that I didn't lose the /var filesystem, this
time...but I did lose the database that I had just created (no data in it,
though, so it works out ok. <G>).
xfs_repair did help, though.
On Fri, 7 Sep 2001, Mike Burger wrote:
> On Fri, 7 Sep 2001, Eric Sandeen wrote:
>
> > Mike Burger wrote:
> > >
> > > Well, yesterday it was the disappearance of everything in the /var
> > > directory. I shutdown and rebooted the system, and received a message
> > > during boot that /dev/hdb1 couldn't be mounted due to missing file system
> > > or bad superblock.
> >
> > Hm, that's a generic mount error message that will happen for a variety
> > of reasons...
> > Sort of "windows-esque" if you ask me. :)
>
> Well, Windows used to be on the hard drive, but it's a non-booting slave,
> drive, now...dedicated entirely to XFS and Linux.
>
> > Any other messages in the syslogs when you try to mount it?
>
> No way for me to know...since it's the drive that houses /var, I can't get
> to the syslogs.
>
> I can reboot and note the errors that come up during boot. Most of them
> involve not being able to find the appropriate dirctories under /var for
> lock files, PID files, etc.
>
> > > df showed mounts of /dev/hda1 (/boot), /devhda2 (/) and /dev/hdc1 (/home).
> > >
> > > I tried, just for kicks, to fsck /dev/hdb1, but it came back with a
> > > message about a bad superblock (as it should have.)
> >
> > Actually, fsck should have run fsck.xfs, which is pretty simple:
>
> I kinda thought so, too...
>
> > > I then tried to
> > > mkfs.xfs /dev/hdb1, and it came back with a message that there was
> > > already an XFS filesystem on the device.
> >
> > Well, that's good news...
>
>
>
> > I suppose it's pretty possible that it is a bad disk, just wondered what
> > you had run into.
>
> I'll be rebooting into single user mode and trying xfs.repair on the drive
> when I get home...I'll let you know what I come up with, if anything.
>
>
|