> :
> :cvsuped 18 aug 1999 00:35 MSD
> :
>
> I would definitely update it, but that may not be your problem.
>
> If you could email your mount setup (df output) and your kernel
> configuration (dmesg output) I would appreciate it.
>
> If you are running softupdates, try turning i
> :
> :cvsuped 18 aug 1999 00:35 MSD
> :
>
> I would definitely update it, but that may not be your problem.
>
> If you could email your mount setup (df output) and your kernel
> configuration (dmesg output) I would appreciate it.
>
> If you are running softupdates, try turning
:>> "AGB" == Alex G Bulushev writes:
:
:>> If you are running softupdates, try turning it off (but I doubt this
:>> is the problem).
:
:AGB> we dont run softupdate because of posible problems with nfs+softupdate
:
:Hmm, I intend to setup a FreeBSD NFS server, and was planning to use
:
>> "AGB" == Alex G Bulushev writes:
>> If you are running softupdates, try turning it off (but I doubt this
>> is the problem).
AGB> we dont run softupdate because of posible problems with nfs+softupdate
Hmm, I intend to setup a FreeBSD NFS server, and was planning to use
softupdate
:>> "AGB" == Alex G Bulushev <[EMAIL PROTECTED]> writes:
:
:>> If you are running softupdates, try turning it off (but I doubt this
:>> is the problem).
:
:AGB> we dont run softupdate because of posible problems with nfs+softupdate
:
:Hmm, I intend to setup a FreeBSD NFS server, and w
>> "AGB" == Alex G Bulushev <[EMAIL PROTECTED]> writes:
>> If you are running softupdates, try turning it off (but I doubt this
>> is the problem).
AGB> we dont run softupdate because of posible problems with nfs+softupdate
Hmm, I intend to setup a FreeBSD NFS server, and was planni
> :
> :cvsuped 18 aug 1999 00:35 MSD
> :
>
> I would definitely update it, but that may not be your problem.
>
> If you could email your mount setup (df output) and your kernel
> configuration (dmesg output) I would appreciate it.
>
> If you are running softupdates, try turning i
> :
> :cvsuped 18 aug 1999 00:35 MSD
> :
>
> I would definitely update it, but that may not be your problem.
>
> If you could email your mount setup (df output) and your kernel
> configuration (dmesg output) I would appreciate it.
>
> If you are running softupdates, try turning
:
:cvsuped 18 aug 1999 00:35 MSD
:
I would definitely update it, but that may not be your problem.
If you could email your mount setup (df output) and your kernel
configuration (dmesg output) I would appreciate it.
If you are running softupdates, try turning it off (but I doubt t
:
:cvsuped 18 aug 1999 00:35 MSD
:
I would definitely update it, but that may not be your problem.
If you could email your mount setup (df output) and your kernel
configuration (dmesg output) I would appreciate it.
If you are running softupdates, try turning it off (but I doubt
> > we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
> > all with 3.2-stable
>
> The most typical cause for these crashes is hardware-induced memory
> corruption, caused by bad memory, a faulty or misconfigured motherboard
> or an overclocked CPU. Are you performing any computation
>
> :we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
> :all with 3.2-stable
> :
>
> Exactly how recent are your kernel sources / kernel build? There have
> been a significant number of fixes to NFS in the last few weeks.
cvsuped 18 aug 1999 00:35 MSD
>
>
> > we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
> > all with 3.2-stable
>
> The most typical cause for these crashes is hardware-induced memory
> corruption, caused by bad memory, a faulty or misconfigured motherboard
> or an overclocked CPU. Are you performing any computatio
:we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
:all with 3.2-stable
:
Exactly how recent are your kernel sources / kernel build? There have
been a significant number of fixes to NFS in the last few weeks.
-Matt
To Unsubscribe: se
> we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
> all with 3.2-stable
The most typical cause for these crashes is hardware-induced memory
corruption, caused by bad memory, a faulty or misconfigured motherboard
or an overclocked CPU. Are you performing any computational work on
we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
all with 3.2-stable
server panics one/two time a day with:
panic: ufs_dirbad: bad dir
then reboot ...
another panic:
panic: vm_fault: fault on nofault entry, addr: ce4c9000
in this case server write:
syncing disks...
and hangs ...
>
> :we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
> :all with 3.2-stable
> :
>
> Exactly how recent are your kernel sources / kernel build? There have
> been a significant number of fixes to NFS in the last few weeks.
cvsuped 18 aug 1999 00:35 MSD
>
>
:we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
:all with 3.2-stable
:
Exactly how recent are your kernel sources / kernel build? There have
been a significant number of fixes to NFS in the last few weeks.
-Matt
To Unsubscribe: s
> we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
> all with 3.2-stable
The most typical cause for these crashes is hardware-induced memory
corruption, caused by bad memory, a faulty or misconfigured motherboard
or an overclocked CPU. Are you performing any computational work on
we use hightly loaded nfsv3/udp server with 5 fbsd nfs client
all with 3.2-stable
server panics one/two time a day with:
panic: ufs_dirbad: bad dir
then reboot ...
another panic:
panic: vm_fault: fault on nofault entry, addr: ce4c9000
in this case server write:
syncing disks...
and hangs ..
20 matches
Mail list logo
