All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org
To: Luca Berra <bluca-APJUtua8uzqonA0d6jMUrA@public.gmane.org>
Cc: "initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Dracut NFS root rw before pivot but ro after pivot
Date: Fri, 08 Oct 2010 10:07:27 +1100	[thread overview]
Message-ID: <20101008100727.16265uf7e1ry9okw@webmail.zoltak.com> (raw)
In-Reply-To: <20101007072427.GA30734-hdG+WfPrfN2JmafXlB/IVQ@public.gmane.org>

Quoting Luca Berra <bluca-APJUtua8uzqonA0d6jMUrA@public.gmane.org>:

> On Thu, Oct 07, 2010 at 12:29:35PM +1100, daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org wrote:
>> If I cd /sysroot/tmp (as I did previously) and ../bin/touch test  
>> the test file is created however the permissions are nobody:nobody:
>>
>> -rw---- 1 nobody nobody 0 Oct    7 11:47 test
>
> you are probably exporting the nfs root without the no_root_squash flag
> check your nfs server configuration
>

Thanks Luca - I'm using a NetApp filer. I had to provide the UID for  
the root user in the export setup.

Normally I don't need to do this. Do you know why in this situation  
the mount is treated differently?

Everything is working with NFSv3 however when I use NFSv4 it boots  
fine to pre-pivot the file system is mounted but the ownership is  
reported as MAX_INT and I cannot write to any directory/file owned by  
MAX_INT. I found the bug report  
https://bugzilla.redhat.com/show_bug.cgi?id=570946. Does anyone know  
if this issue has been resolved or there is a work around?

Thanks!



      parent reply	other threads:[~2010-10-07 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  1:42 Dracut NFS root rw before pivot but ro after pivot daniel-2N1FInP7wozQT0dZR+AlfA
     [not found] ` <20101005124250.12811x7b1hr8g23k-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-05  5:52   ` daniel-2N1FInP7wozQT0dZR+AlfA
     [not found]     ` <20101005165245.12962kslvxq6cmyo-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-05  6:48       ` daniel-2N1FInP7wozQT0dZR+AlfA
     [not found]         ` <20101005174817.98833aq1pzqn2cds-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-07  1:29           ` daniel-2N1FInP7wozQT0dZR+AlfA
     [not found]             ` <20101007122935.19334qntub6vdeo0-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-07  7:24               ` Luca Berra
     [not found]                 ` <20101007072427.GA30734-hdG+WfPrfN2JmafXlB/IVQ@public.gmane.org>
2010-10-07 23:07                   ` daniel-2N1FInP7wozQT0dZR+AlfA [this message]

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=20101008100727.16265uf7e1ry9okw@webmail.zoltak.com \
    --to=daniel-2n1finp7wozqt0dzr+alfa@public.gmane.org \
    --cc=bluca-APJUtua8uzqonA0d6jMUrA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.