Issuing reboot:
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
1: buf:0xa0009e10e200, vnode:0, flags:0, blkno:0, lblkno:0, buflock:lock
type bufwait: EXCL by thread 0xe00012741680
On Wed, Feb 21, 2001 at 09:55:22PM +, Josef Karthauser wrote:
> Hi Kirk,
>
> A number of us have problem reliably syncing disks with softupdates in
> recent -current from about the 19th. Is it possible that you broke
> something with your recent commit?
I forgot to mention t
+61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.aims.com.au
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Josef
> Karthauser
> Sent: Thursday, 22 February 2001 8:55
> To: Kirk McKusick
> Cc: [EMAIL PROTECTED]
> Su
Hi Kirk,
A number of us have problem reliably syncing disks with softupdates in
recent -current from about the 19th. Is it possible that you broke
something with your recent commit?
Cheers,
Joe
PGP signature
In message <[EMAIL PROTECTED]>, Kenneth Wayne
Culver writes:
>Alright I did what PHK told me to, and updated, but now for some reason
>when I reboot, I can't get the root directory to keep the new kernel. this
>is what happens before I reboot:
>
>culverk:~> ls -l /kernel*
>-r-xr-xr-x 1 root whe
Alright I did what PHK told me to, and updated, but now for some reason
when I reboot, I can't get the root directory to keep the new kernel. this
is what happens before I reboot:
culverk:~> ls -l /kernel*
-r-xr-xr-x 1 root wheel 1551621 Nov 8 08:18 /kernel*
-r-xr-xr-x 1 root wheel 1551621
achine
>does this:
>
>syncing disks 15 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
>giving up..
>Rebooting...
>
>Then fsck has to fix a whole lot of stuff upon reboot. This is with a
>kernel that is 20 minutes old.
>
>
>==
I just cvsupped this morning, and noticed that now whenever I reboot (I do
this to make sure everything works right with the new kernel) the machine
does this:
syncing disks 15 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12
giving up..
Rebooting...
Then fsck has to fix a whole lot of
> the disks. This went fine, but when he exited from single user mode,
> it again hangs on syncing disks. This is a brand new machine, worked
> great for about 6 weeks - and this is the second machine to do this since
> the first of the year.
I had a similar problem when I upg
suming (we know what
assume means) that this is the same problem.
Tom Veldhouse
ve...@visi.com
-Original Message-
From: T.D. Brace
To: curr...@freebsd.org
Date: Wednesday, February 10, 1999 8:44 AM
Subject: Syncing Disks
>
>Hello,
>
>We have a problem with some 3.0 release
Hello,
We have a problem with some 3.0 release boxes. One just went down two
days ago. When it came back up, it hangs on syncing disks. I had a
tech (it's in a remote location) boot into single user mode, and fsck
the disks. This went fine, but when he exited from single user mode,
it
11 matches
Mail list logo