On Fri, Dec 24, 1999 at 09:14:01PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], David Malone writes:
Should fsck be changed to set the hotroot flag if the block device
is given?
I deliberately didn't do this for several reasons:
1. It would need to know the
In message [EMAIL PROTECTED], David Malone writes:
On Fri, Dec 24, 1999 at 09:14:01PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], David Malone writes:
Should fsck be changed to set the hotroot flag if the block device
is given?
I deliberately didn't do this for several
So running
ls -l /dev | grep '^b'
gives no output ?
Appologies - I must have cocked up. I can't tell what devices I
had there, but there must have been some block devices left. I'd
guess I accidently ran "./MAKEDEV all" twice instead of "./MAKEDEV
*", (either that or I had some
In message [EMAIL PROTECTED], David Malone writes:
Should fsck be changed to set the hotroot flag if the block device
is given?
I deliberately didn't do this for several reasons:
1. It would need to know the bmajor - cmajor translation table.
2. we need some carrot/stick to
Remake your devices in /dev with a fresh MAKEDEV
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL
Remake your devices in /dev with a fresh MAKEDEV
Already done that - 3 times! I even blew away /dev and
rebuilt it from scratch.
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I have the problem on my system using pure scsi disks.
You could try adding printfs to fsck to see if hotroot is being
set and see if fsck is reloading the filesystem. You want to look
in main.c (search for RELOAD) and preen.c (search for hotroot++).
David.
To Unsubscribe: send mail
In message [EMAIL PROTECTED], David Malone writes:
Remake your devices in /dev with a fresh MAKEDEV
Already done that - 3 times! I even blew away /dev and
rebuilt it from scratch.
So running
ls -l /dev | grep '^b'
gives no output ?
--
Poul-Henning Kamp FreeBSD coreteam
So running
ls -l /dev | grep '^b'
gives no output ?
I'll check and see - initially I did a "./MAKEDEV *" and then
the first time I had problems after that I tried a "./MAKEDEV all".
I think the two of these should have replaced all the old devices?
I still had problems after that,
I think I have a partial explaination of the fsck not working on
the first try, and a reboot fixing it.
I've been using Soren's new driver for some time, and did a MAKEDEV
after the block device changes, but I found that it I booted with
a dirty root filesystem then fsck would fix the problem,
On Thu, 23 Dec 1999, David Malone wrote:
The problem seems to be that I'm listing the "/dev/wd1s1a" devices
in fstab instead of "/dev/ad1s1a", and fsck doesn't recognise that
they are the same thing, and so doesn't spot that it needs to set
the hotroot flag.
I'm not sure if this is purely
I have the problem on my system using pure scsi disks.
My fstab entry:
# DeviceMountpoint FStype Options DumpPass#
/dev/da0s2b noneswapsw 0 0
/dev/da1s1b noneswapsw 0 0
On Sun, Dec 19, 1999 at 11:28:29PM -0500, Bill Fumerola wrote:
On Sun, 19 Dec 1999, Alex Zepeda wrote:
Hmm. It happened again. This time I was playing around with the vmware
stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think
this is the way to go, not bloating
On Sun, 19 Dec 1999, Mike Smith wrote:
On Sun, 19 Dec 1999, Alex Zepeda wrote:
Ditto. mount was telling me my fs wasn't clean, but after I rebooted
it was fine and it didn't fsck that second time.
Bruce posted (but did not commit) what may be a fix for this a while back:
I wish he
Hmm. It happened again. This time I was playing around with the vmware
stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think
this is the way to go, not bloating *our* procfs), and eventually when run
panic'd the system. I just rebooted it (nearly a day later), and fsck
On Sun, 19 Dec 1999, Alex Zepeda wrote:
Hmm. It happened again. This time I was playing around with the vmware
stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think
this is the way to go, not bloating *our* procfs), and eventually when run
panic'd the system. I just
On Sun, 19 Dec 1999, Alex Zepeda wrote:
Hmm. It happened again. This time I was playing around with the vmware
stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think
this is the way to go, not bloating *our* procfs), and eventually when run
panic'd the system. I
17 matches
Mail list logo
