In article ,
John D. Baker wrote:
>I finally got my i386-current systems set up to investigate this further.
>
>One thing I hadn't thought about before is that normally, there is only
>one 'amd' process managing all the automount points.
>
>In the case of the system with processes stuck in "tstile
I finally got my i386-current systems set up to investigate this further.
One thing I hadn't thought about before is that normally, there is only
one 'amd' process managing all the automount points.
In the case of the system with processes stuck in "tstile", something
spawns a second 'amd' proces
On Thu, 11 Feb 2016, John D. Baker wrote:
> One thing I think I should check is to get the client stuck and try to
> umount an NFS file system without deliberately sabotaging the attempt
> (i.e., don't make it PWD before umount). I expect it will get stuck
> as well.
Confirmed. Attempting to un
On Fri, 12 Feb 2016 18:36:04 + (UTC), chris...@astron.com (Christos
Zoulas) wrote:
> Is your kernel DEBUG/DIAGNOSTIC/LOCKDEBUG? Do you have a netbsd.gdb
> for it? Can you get a crash dump when it is stuck?
On the most convenient test platform, "No," "Yes," and "No."
My kernels are based on
In article <20160212103705.7ba5d115...@xen1.duzan.org>,
Gary Duzan wrote:
>In Message ,
> "John D. Baker" wrote:
>
>=>On Fri, 12 Feb 2016 03:08:04 + (UTC), chris...@astron.com (Christos
>=>Zoulas) wrote:
>=>
>=>> Ok, do a cvs update (which is what triggers it), wait a bit and then
>=>> do th
In Message ,
"John D. Baker" wrote:
=>On Fri, 12 Feb 2016 03:08:04 + (UTC), chris...@astron.com (Christos
=>Zoulas) wrote:
=>
=>> Ok, do a cvs update (which is what triggers it), wait a bit and then
=>> do the unmount.
=>
=>I'm not quite sure about to what you refer. On a non-stuck client,
On Fri, 12 Feb 2016 03:08:04 + (UTC), chris...@astron.com (Christos
Zoulas) wrote:
> Ok, do a cvs update (which is what triggers it), wait a bit and then
> do the unmount.
I'm not quite sure about to what you refer. On a non-stuck client,
during 'cvs update' on the NFS server or even arbitra
In article ,
John D. Baker wrote:
>On Fri, 12 Feb 2016 01:19:59 + (UTC), chris...@astron.com (Christos
>Zoulas) wrote:
>
>> So the problem is when nfs unmounts. You should be able to reproduce
>> it
>
>> mount foo:/foo /foo
>> cd /foo
>> umount /foo
>
>> And now umount is stuck and neve
On Fri, 12 Feb 2016 01:19:59 + (UTC), chris...@astron.com (Christos
Zoulas) wrote:
> So the problem is when nfs unmounts. You should be able to reproduce
> it
> mount foo:/foo /foo
> cd /foo
> umount /foo
> And now umount is stuck and never returns EBUSY. Is that true?
On the machine
In article ,
John D. Baker wrote:
>On Wed, 10 Feb 2016, John D. Baker wrote:
>
>> On Wed, 10 Feb 2016 18:43:38 + (UTC), chris...@astron.com (Christos
>> Zoulas) wrote:
>>
>> > Unfortunately looks like you'll have to reboot and redo the test to
>> > answer this.
>>
>> To make it unambiguous,
On Wed, 10 Feb 2016, John D. Baker wrote:
> On Wed, 10 Feb 2016 18:43:38 + (UTC), chris...@astron.com (Christos
> Zoulas) wrote:
>
> > Unfortunately looks like you'll have to reboot and redo the test to
> > answer this.
>
> To make it unambiguous, I'll definitely arrange to do this again.
O
On Wed, 10 Feb 2016 18:43:38 + (UTC), chris...@astron.com (Christos
Zoulas) wrote:
> John D. Baker wrote:
> > amd: pid 5064 proc c1852004 vmspace/map c19034fc flags 0
> Amd is trying to unmount a filesystem and is stuck in genfs_lock
> And the million $ question is:
> Is amd trying to
In article ,
John D. Baker wrote:
>On Wed, 10 Feb 2016 16:08:10 + (UTC), chris...@astron.com (Christos
>Zoulas) wrote:
>
>ksh: pid 557 proc c1c6a87c vmspace/map c1903778 flags 4000
Ksh tries to open a file and gets stuck in genfs_lock.
>df: pid 4402 proc c18b9008 vmspace/map c19039f4 fla
On Wed, 10 Feb 2016 16:08:10 + (UTC), chris...@astron.com (Christos
Zoulas) wrote:
> John D. Baker wrote:
>> I should note that the recent nfs-related pull-ups to netbsd-7 are on
>> all clients but the server has not yet been updated.
> Can you run crash(8) on the live system and get backtr
In article ,
John D. Baker wrote:
>I should note that the recent nfs-related pull-ups to netbsd-7 are on
>all clients but the server has not yet been updated.
Can you run crash(8) on the live system and get backtraces of the
stuck processes?
christos
I've lately noticed a very annoying behavior using recently-updated
NetBSD-7 and 'firefox-43.0nb1' from pkgsrc-2015Q4.
Client machine using 'amd' to mount home directory from file server.
Run 'firefox' on client machine.
Perform 'cvs update' on file server with trees on same filesystem
served fo
16 matches
Mail list logo
