On Mon, 20 Aug 2007, Steinar H. Gunderson wrote:
On Mon, Aug 20, 2007 at 03:08:00PM -0400, Justin Piszcz wrote:
Very impressive! This solves the find problem, I will let you know if I
have any other issues.
Great to hear that it's probably the same problem. :-)
Is it safe to keep that ve
On Mon, Aug 20, 2007 at 03:08:00PM -0400, Justin Piszcz wrote:
> Very impressive! This solves the find problem, I will let you know if I
> have any other issues.
Great to hear that it's probably the same problem. :-)
> Is it safe to keep that version installed until the new-fixed version is
>
On Mon, 20 Aug 2007, Steinar H. Gunderson wrote:
On Mon, Aug 20, 2007 at 12:15:50PM -0400, Justin Piszcz wrote:
Could you please remind me of the command? apt-get install -t unstable
nfs-kernel-server nfs-common?
Assuming you've got unstable in your sources.list, that should do fine. (You
d
On Mon, Aug 20, 2007 at 12:15:50PM -0400, Justin Piszcz wrote:
> Could you please remind me of the command? apt-get install -t unstable
> nfs-kernel-server nfs-common?
Assuming you've got unstable in your sources.list, that should do fine. (You
don't really want to be using apt-get in 2007, thoug
On Mon, 20 Aug 2007, Steinar H. Gunderson wrote:
On Mon, Aug 20, 2007 at 04:45:20AM -0400, Justin Piszcz wrote:
Need to dig into this, it now happens on an x86 box, in particular, when
you run find // across the root filesystem.
This sounds awfully lot like a duplicate of #435056. Could you
On Mon, Aug 20, 2007 at 04:45:20AM -0400, Justin Piszcz wrote:
> Need to dig into this, it now happens on an x86 box, in particular, when
> you run find // across the root filesystem.
This sounds awfully lot like a duplicate of #435056. Could you try the latest
sid version and see if it fixes you
On Sun, 19 Aug 2007, Justin Piszcz wrote:
On Sun, 19 Aug 2007, Steinar H. Gunderson wrote:
On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote:
Using these for now and without fsid=, will see if it happens again.
OK. Are you implying that this only happens every now and then?
On Sun, 19 Aug 2007, Steinar H. Gunderson wrote:
On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote:
Using these for now and without fsid=, will see if it happens again.
OK. Are you implying that this only happens every now and then? From your
initial description, it sounded like
On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote:
> Using these for now and without fsid=, will see if it happens again.
OK. Are you implying that this only happens every now and then? From your
initial description, it sounded like it was consistent. An strace of
rpc.mountd at the mom
On Sat, 18 Aug 2007, Justin Piszcz wrote:
On Thu, 16 Aug 2007, Justin Piszcz wrote:
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote:
On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote:
Unsure, I have mounted with the options I mentioned earlier and that
seems
to have resol
On Thu, 16 Aug 2007, Justin Piszcz wrote:
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote:
On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote:
Unsure, I have mounted with the options I mentioned earlier and that seems
to have resolved the problems, all partitions are SW RAID 1
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote:
On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote:
Unsure, I have mounted with the options I mentioned earlier and that seems
to have resolved the problems, all partitions are SW RAID 1 and 5 and the
mount daemon/etc does not appear
On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote:
> Unsure, I have mounted with the options I mentioned earlier and that seems
> to have resolved the problems, all partitions are SW RAID 1 and 5 and the
> mount daemon/etc does not appear to know how to deal with them after last
> we
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote:
On Thu, Aug 16, 2007 at 03:58:15AM -0400, Justin Piszcz wrote:
Arch = x86_64
And does a downgrade help?
/* Steinar */
--
Homepage: http://www.sesse.net/
Unsure, I have mounted with the options I mentioned earlier and that seems
to have r
On Thu, Aug 16, 2007 at 03:58:15AM -0400, Justin Piszcz wrote:
> Arch = x86_64
And does a downgrade help?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, 16 Aug 2007, Steinar H. Gunderson wrote:
On Sun, Aug 12, 2007 at 04:37:01PM +0200, Steinar H. Gunderson wrote:
Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
breaks rpc.mountd? That sounds very weird, as there's been exactly zero
changes to mountd in that t
On Sun, Aug 12, 2007 at 04:37:01PM +0200, Steinar H. Gunderson wrote:
>>> Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
>>> breaks rpc.mountd? That sounds very weird, as there's been exactly zero
>>> changes to mountd in that timeframe...
>> Well I did not change anythi
On 8/12/07, Steinar H. Gunderson <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote:
> > I'm using Debian sid and I upgraded the system today
> > (the last complete upgrade was about one month ago).
> > I get the "failed to contact portmap" errors.
>
> Is t
On Sun, Aug 12, 2007 at 09:35:48PM -0500, Nelson Castillo wrote:
> BTW, the NFS troubleshooting documentation references a rcpinfo binary.
> Is it obsoleted? Perhaps I need to install another package.
You probably mean rpcinfo. It's included in the libc6 package, so it's
definitely on your system.
In 8/12/07, Steinar H. Gunderson <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote:
> > I'm using Debian sid and I upgraded the system today
> > (the last complete upgrade was about one month ago).
> > I get the "failed to contact portmap" errors.
>
> Is t
On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote:
> I'm using Debian sid and I upgraded the system today
> (the last complete upgrade was about one month ago).
> I get the "failed to contact portmap" errors.
Is the portmapper running at all? (ps aux | grep portmap)
> I am stuck. I
Hi.
I'm using Debian sid and I upgraded the system today
(the last complete upgrade was about one month ago).
I get the "failed to contact portmap" errors.
nfsd: unexporting all filesystems
RPC: failed to contact portmap (errno -5).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
On Sun, Aug 12, 2007 at 10:34:13AM -0400, Justin Piszcz wrote:
>> Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
>> breaks rpc.mountd? That sounds very weird, as there's been exactly zero
>> changes to mountd in that timeframe...
> Well I did not change anything on the c
On Sun, 12 Aug 2007, Steinar H. Gunderson wrote:
On Sun, Aug 12, 2007 at 04:08:21AM -0400, Justin Piszcz wrote:
2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-4
2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-11
Uhm, are you saying that upgrading the server from
On Sun, Aug 12, 2007 at 04:08:21AM -0400, Justin Piszcz wrote:
> 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-4
> 2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-11
Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
breaks rpc.mountd? That sou
On Sun, 12 Aug 2007, Steinar H. Gunderson wrote:
On Sat, Aug 11, 2007 at 06:53:39PM -0400, Justin Piszcz wrote:
After apt-get upgrade, NFS no longer works:
Did you upgrade the server or the client? Which version did you upgrade from?
What does your /etc/exports look like?
/* Steinar */
--
On Sat, Aug 11, 2007 at 06:53:39PM -0400, Justin Piszcz wrote:
> After apt-get upgrade, NFS no longer works:
Did you upgrade the server or the client? Which version did you upgrade from?
What does your /etc/exports look like?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE,
Package: nfs-kernel-server
Version: 1.1.0-11
Running: Debian Testing
Kernel: 2.6.22
After apt-get upgrade, NFS no longer works:
[ 2059.998309] nfs: server p34 not responding, still trying
[ 2289.314682] nfs: server l2 not responding, still trying
Aug 11 18:06:27 p34 mountd[6828]: Cannot export
28 matches
Mail list logo
