From: "JaniD++" <djani22@dynamicweb.hu>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
Date: Sun, 4 Dec 2005 15:45:12 +0100 [thread overview]
Message-ID: <011201c5f8e1$557c32a0$0400a8c0@dcccs> (raw)
In-Reply-To: 1133622663.7911.5.camel@lade.trondhjem.org
----- Original Message -----
From: "Trond Myklebust" <trond.myklebust@fys.uio.no>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, December 03, 2005 4:11 PM
Subject: Re: 2.6.15-rc3: adduser: unable to lock password file
> On Sat, 2005-12-03 at 14:00 +0100, JaniD++ wrote:
>
> > Here is the strace-s output: (20KB)
> > http://download.netcenter.hu/bughunt/20051203/adduser.log
> >
> > This problem is always on on 2.6.15-rc3, and newer on 2.6.14.2
>
> OK... Looks like it is bailing out after the lines
>
> link("/etc/passwd.2522", "/etc/passwd.lock") = 0
> stat64("/etc/passwd.2522", {st_mode=S_IFREG|0600, st_size=5, ...}) = 0
>
> I'll bet the stat64 is filing to show that the file now has 2 links.
>
> As a first step, could you please grab the 2 patches
>
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-01-nfs-cache-init.dif
> and
>
http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc4/linux-2.6.15-02-fix_cache_consistency.dif
>
> and see if they fix the problem?
done.
No change. :(
Cheers,
Janos
>
> Cheers,
> Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-12-04 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 22:47 2.6.15-rc3: adduser: unable to lock password file JaniD++
2005-12-02 0:02 ` Trond Myklebust
2005-12-02 10:55 ` JaniD++
2005-12-02 11:08 ` Marc Koschewski
2005-12-02 11:26 ` JaniD++
2005-12-03 13:00 ` JaniD++
2005-12-03 15:11 ` Trond Myklebust
2005-12-04 14:45 ` JaniD++ [this message]
2005-12-04 14:53 ` Trond Myklebust
2005-12-05 23:14 ` JaniD++
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='011201c5f8e1$557c32a0$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox