Hi Juergen,
My email address has changed so don't be alarmed if your CC bounces. :)
An update of grub2 is long overdue, so I'll work on that right now.
-Rick
On 2012/07/21 11:58, Juergen Lock wrote:
> Hi!
>
> I'm in the process of testing 9.1 on the laptop where I use
> Rick Macklem wrote:
>
> > Sun did add a separate file locking protocol called the NLM
> > or rpc.lockd if you prefer, but that protocol design was
> > fundamentally flawed imho and, as such, using it is in the
> > "your mileage may vary" category
how the backup was done. To avoid "stale handle"
the backup/reload had to retain the same i-nodes, including the generation
number in them. (But, then, those 1980s SMD disks never trashed the
file systems, or did they?:-)
You shouldn't get me reminising on the good ole days, rick
_
are correct w.r.t. the above statement. (ie. Sun's
official position vs something I heard.)
Anyhow, appologies if I gave the impression that I was correcting your
statement. My intent was just to throw out another statement that I
vaguely recalled someone an Sun stating.
rick
___
> On 7 January 2011 08:16, Rick Macklem wrote:
>
> > When I said I recalled that they didn't do TCP because of excessive
> > overhead, I forgot to mention that my recollection could be wrong.
> > Also, I suspect you are correct w.r.t. the above statement. (ie.
>
NS failure occurs is a particularily
good idea, mostly because it doesn't help for critical mounts. (I haven't looked
to see if the change is feasible, either.)
It would be nice to get DNS working more reliably early in boot and the,
of course, there is what Doug stated w.r.t. use IP number
ver is an up-to-date Linux Debian 5 with kernel 2.6.26.
>
I'm afraid I can't blame Linux (at least not until we have more info;-).
> If more info is needed. I can easily reproduce this.
See above #2.
Good luck with it and let us know how it goes, rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
locked are concurrently
shared with other clients.) I don't know if this would fix your diskless
problem.
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
TABLE 870K 5.2M 1.8M
> wonderland/8.1-STABLE 496K 690K 420K
> wonderland/8.2-PRERELEASE 800K 1.2M 447K
>
> Furthermore, I was still able to induce the NFS "server not
> responding"
> message with 8.2-PRERELEASE. So I applied the patch from Rick Macklem.
> The thr
ound, retrying the RPC.)
> 2. I have dumps and stuff. I will mail some links in private e-mail.
I'll take a look at some point.
> 3. Didn't work. It mount, but ls -l /home gives "Operation not
> permitted".
>
It should work. This hints at a se
in EIO from a server exporting
Oops, I meant "Without the patch a stale file handle...", rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> Hello Rick,
>
> Am 11.11.2010 23:54, schrieb Rick Macklem:
> > That patch is "self contained", so I think it should be fine to
> > apply it
> > to an 8.0 server.
> >
> > You might also want
> >
> > http://people.freebsd.org/~rmac
still observing.
Thanks for letting us know, rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
() uses MGET(, M_DONTWAIT,)
which can fail when mbuf allocation is constrainted, for example.)
Thanks to john.gemignani at isilon.com for spotting this problem, rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
/8
as r217527. This krpc patch is also available at:
http://people.freebsd.org/~rmacklem/krpc.patch
Thanks go to John Gemignani for spotting this bug in the krpc code.
It will not be in 8.2, so please grab the patch if you are using either
NFS client in any FreeBSD8.n system, rick
__
ur so that it tries to
get an unused port for each of the 4 cases.
(This all applies to the "wildcard" case, where no port# or
hosts have been specified as command args.)
If you have the chance to try these patches, please let us know
how they work for you?
rick
ps: I lost track of the thr
> On 02/18/2011 10:08, Rick Macklem wrote:
> > The attached patches changes the behaviour so that it tries to
> > get an unused port for each of the 4 cases.
>
> Am I correct in assuming that what you're proposing is to
> (potentially)
> have different ports
fixes the only places in the
client side krpc over udp that seems mights cause a leak. I have no
idea if it will help, since these cases should rarely, if ever,
happen in practice.
Please let us know if you have the chance to try the patch and
whether or not it helped.
rick
--- rpc/cln
> Hi--
>
> On Feb 19, 2011, at 1:16 PM, Rick Macklem wrote:
> > Well, that was what I was proposing. I could be wrong, but as far as
> > I
> > know, this is allowed by Sun RPC. The port#s are assigned
> > dynamically and
> > registered with rpcbind. (I
> On 02/19/2011 13:16, Rick Macklem wrote:
> >> On 02/18/2011 10:08, Rick Macklem wrote:
> >>> The attached patches changes the behaviour so that it tries to
> >>> get an unused port for each of the 4 cases.
> >>
> >> Am I correct in assum
> --- On Sun, 2/20/11, Rick Macklem wrote:
>
> > From: Rick Macklem
> > Subject: Re: NFS client over udp
> > To: "Kirill Yelizarov"
> > Cc: freebsd-stable@freebsd.org
> > Date: Sunday, February 20, 2011, 9:02 PM
> > > --- On Fri, 2/18/11,
> --- On Tue, 2/22/11, Rick Macklem wrote:
>
> > From: Rick Macklem
> > Subject: Re: NFS client over udp
> > To: "Kirill Yelizarov"
> > Cc: freebsd-stable@freebsd.org
> > Date: Tuesday, February 22, 2011, 2:10 AM
> > > --- On Sun, 2/20/11
> Rick,
> I have good news. I upgraded to 8.2-stable and i ran all four
> different tests (nfs client new and old and over udp and tcp) and
> found that there is no leak in either. ALl of them behave almost the
> same, i couldn't find any difference. The speed i achieved on
that port to be available
for the other 3 combinations of UDP/TCP x IPv6/IPv4.
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> >> On 02/18/2011 10:08, Rick Macklem wrote:
> >> > The attached patches changes the behaviour so that it tries to
> >> > get an unused port for each of the 4 cases.
> >>
> >> can you send me the patches?
> >> thanks,
> >> danny
mpletely impossible
> to
> find a port that's open on all 4 families?
>
> > I saw Doug's commnent, and also the:), it's not as simple as
> > tracking port
> > 80 or 25, needs some efford, but it's deterministic/programable, and
> > worst case
&g
gt; >>> what?
> >>
> >> Can you please describe the scenario when it's completely
> >> impossible to
> >> find a port that's open on all 4 families?
> > i did not say impossible, concidering that Rick asked how many times
> > he
>
r issue to
me?
So, is it just NFS that wedges or all IP activity and does NFS come
back to life after the "ifconfig XX up"?
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
Hi,
Just a heads up that after a commit going into stable/8 in a few
minutes, you'll need to do a fresh kernel build, starting at
"config GENERIC", including rebuilding the NFS related modules.
rick
___
freebsd-stable@freebsd.org ma
> On Sat, May 14, 2011 at 08:05:41PM -0400, Rick Macklem wrote:
> > Just a heads up that after a commit going into stable/8 in a few
> > minutes, you'll need to do a fresh kernel build, starting at
> > "config GENERIC", including rebuilding the NFS related modu
> On 05/14/11 20:05, Rick Macklem wrote:
> > Hi,
> >
> > Just a heads up that after a commit going into stable/8 in a few
> > minutes, you'll need to do a fresh kernel build, starting at
> > "config GENERIC", including
> > On May 19, 2011, at 6:53 PM, Rick Macklem wrote:
> > Assuming that you are using the regular 8.n client (and not the new
> > one), there have been some commits related to krpc bugs that could
> > have
> > fixed cases which would have caused poor perf., although al
inder w.r.t. this.)
Should I MFC this to stable/8?
(I had assumed that I should leave them in
the old location for backwards compatibility and therefore wasn't going to
MFC deletion of them in /usr/include/nfsclient. If I MFC that, the entries
for them in ObsoleteFiles.inc for /usr/include/n
>
> At this moment make installworld only installs the headers in the new
> location,
> on both 8/stable and head/current. On 8/stable they are immediately
> removed
> again when running make delete-old, because they are in
> ObsoleteFiles.inc.
> On head/current they are left alone, they are not i
cially
if could catch duplicates) for people to look at might be nice. The list
would get long (and not really indicate how well the hardware worked), but
at least it would be up-to-date and not require manual maintenance.
I'm not volunteering to do this;-) although I'm retired too, but it
(I'm wondering about this one, since the problem seems to happen
when the file's size has been truncated.)
Herve Boulouis, if you want to see what r223054 changes, just go to
http://svn.freebsd.org/viewvc/stable/8/sys/nfsclient
and then click on nfs_bio.c.
(The changes are sma
think we're going to make any progress on this in the current
> state so I think we'll give it a shot.
>
Just a random thought that is probably not relevent, but...
Is it possible that some change for the upgrade is making the machines
run hotter and they're failing when they
t -n 64"
If you have too many of them, the extra ones just sit waiting for a request and
don't take up many resources. On the other hand, if you don't have enough of
them, requests will get backed up in the socket's receive queue.
I'll also mention considering
nfsd: service??? mi_switch+0x176
> > > sleepq_catch_signals+0x309 sleepq_timedwait_sig+0x12
> > > _cv_timedwait_sig+0x11d svc_run_internal+0x939
> > > svc_thread_start+0xb fork_exit+0x114 fork_trampoline+0xe
> > >
> > >
> > >
> > >
s because the NFS clients don't know
to hold onto the data and re-write it after a server crash/reboot.
rick
ps: NFS write performance has been an issue since SUN released their
first implementation of it in 1985. The "big" server vendors typically
solve the problem with lots o
ok to see if TCP segments are being lost/retransmitted.
(Although wireshark knows NFS and is nice for this, because it shows
relative sequence numbers, the TCP dump will show you the TCP level
retries, etc.)
Good luck with it, rick
> P.S. A lot of other 9.0 features look very nice indeed!
>
ints to /usr/src/usr/src.
>
> What you /etc/exports could look like (the way it works for me,
> doesn't
> mean that it's correct though):
>
> /usr/src
> V4: / -sec=krb5:krb5i:krb5p
>
>
> Yuri
Btw, Guilio, your email address bounces for me, so hopefully you
problem with doing this is that, for ZFS, you then have to export
all file systems from "/" down to where you want to mount. (Again,
these are done by export lines separate from the "V4:" line.)
If you specify:
V4: /usr/src -sec=krb5:krb5i:krb5p
/usr/src -sec=krb5:krb5i:krb5p
Giulio Ferro wrote:
> I'm trying to setup a kerberized NFS system made of a server and a
> client (both freebsd 9 amd64 stable)
>
> I've tried to follow this howto:
> http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup
>
> But couldn't get much out of it.
>
> First question : is th
for the user you are logged in as
- Now, try a kerberos mount, as follows:
% mount -t nfs -o nfsv4,sec=krb5 :/ /
- if that works
% cd /
% ls -l
If these last steps fail, it is not easy to figure out why.
(Look in /var/log/messages for any errors. If you get what
the gssd calls an minor status, that is th
client after
it receives the name. (For Getattr, the server should translate uid/gid
to @ and then the client should turn that back
into the same uid/gid.)
Good luck with it, rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
line, I think the newnfs client (the default for 9.0) can
do this, but I'm doubtful the old/reguler one can. (I also wouldn't
be surprised if there is still a bug other than the above mentioned
one w.r.t. doing a "umount /mnt" and getting that hung before trying
"umount -f /mnt&
Doug Barton wrote:
> On 02/13/2012 18:23, Rick Macklem wrote:
> > Doug Barton wrote:
> >> Is there some magic I'm missing to convince an 8.2 system to umount
> >> -f?
> >> I had an NFS server crash, so I'm trying to get the mounts updated.
> >
Doug Barton wrote:
> On 02/13/2012 18:23, Rick Macklem wrote:
> > Doug Barton wrote:
> >> Is there some magic I'm missing to convince an 8.2 system to umount
> >> -f?
> >> I had an NFS server crash, so I'm trying to get the mounts updated.
> >
Doug Barton wrote:
> On 02/13/2012 19:13, Rick Macklem wrote:
> > I just looked and at least some of the fixes were MFC'd to stable/8
> > about
> > 8months ago. So, they aren't in 8.2, but will be in 8.3.
>
> Well 8.3 is about to enter code freeze, any way w
Giulio Ferro wrote:
> Thanks everybody again for your help with setting up a working
> kerberized nfsv4 system.
>
> I was able to user-mount a nfsv4 share with krb5 security, and I was
> trying to do the same as root.
>
> Unfortunately the patch I found here:
> http://people.freebsd.org/~rmacklem
ytab entry won't work unless
it is set correctly.
Good luck with it, rick
> Is there a more recent patch available or some better way to
> automatically
> mount the share at boot time?
>
> Thanks again.
> ___
> freebsd-st
Jeremie Le Hen wrote:
> Hi list,
>
> Can you please Cc: me when replying as I'm not subscribed, thanks.
>
> I have a problem with procmail which gets a "File too large" error
> when
> it tries to write at the end of some mailbox file.
>
> I truss'ed it and I found the following:
>
> % stat("/ho
Jeremie Le Hen wrote:
> Hi Rick,
>
> On Sun, Feb 19, 2012 at 07:46:42PM -0500, Rick Macklem wrote:
> > > This is a 8.2 32 bits jail on a 8.2 amd64 host. In the jail, /home
> > > is
> > > a
> > > nullfs mounted ZFS filesystem. The mailbox is not th
x27;d jhb@ since he seems to have been
the author of the sleep() stuff.
Anyhow, please try the attached patch which replaces the mtx_unlock();
tsleep(); with
msleep()s using PDROP. If the attachment gets lost, the patch is also here:
http://people.freebsd.org/~rmacklem/tsleep.patch
Thanks for
John Baldwin wrote:
> On Wednesday, February 22, 2012 2:24:14 pm Konstantin Belousov wrote:
> > On Wed, Feb 22, 2012 at 11:29:40AM -0500, Rick Macklem wrote:
> > > Hiroki Sato wrote:
> > > > Hi,
> > > >
> > > > Just a report, but I go
Konstantin Belousov wrote:
> On Wed, Feb 22, 2012 at 11:29:40AM -0500, Rick Macklem wrote:
> > Hiroki Sato wrote:
> > > Hi,
> > >
> > > Just a report, but I got the following panic on an NFS server
> > > running
> > > 8.3-PRERELEASE:
> &
st being free'd twice.
The bit is erroneously set by "amd" sometimes. If you are using "amd",
that might be related to the resume problem?
rick
ps: I suspect you saw it, but there was a recent thread related to known
suspend/re
it checks for SAVENAME being
set for all cases where uma_zalloc() has allocated a path buffer, so that
no more leaks like this will happen when underlying file systems set
SAVENAME.
rick
--- fs/nfsserver/nfs_nfsdport.c.sav 2012-04-25 16:50:05.0 -0400
+++ fs/nfsserver/nfs_nfsdport.c 2012-04
m/namei-leak.patch
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Oliver Brandmueller wrote:
> Hi,
>
> On Wed, Apr 25, 2012 at 05:34:05PM -0400, Rick Macklem wrote:
> > Good work isolating this!
>
> Thank you!
>
> > I now see the problem. The new NFS server code assumed that
> > VOP_LOOKUP()
> > calls would not set S
Steven Hartland wrote:
> - Original Message -
> From: "Rick Macklem"
> To: "Oliver Brandmueller"
> Cc:
> Sent: Thursday, April 26, 2012 1:24 AM
> Subject: Re: 9-STABLE, ZFS, NFS, ggatec - suspected memory leak
>
>
> > Oliver Brandm
Steven Hartland wrote:
> Original Message -
> From: "Rick Macklem"
> > At a glance, it looks to me like 8.x is affected. Note that the
> > bug only affects the new NFS server (the experimental one for 8.x)
> > when exporting ZFS volumes. (UFS exported
Daniel Braniss wrote:
> > Security_Multipart(Fri_Apr_27_13_35_56_2012_748)--
> > Content-Type: Text/Plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> >
> > Rick Macklem wrote
> > in
> > <1527622626.3418715.1335445225510.javamail.
Daniel Braniss wrote:
> > Daniel Braniss wrote:
> > > > Security_Multipart(Fri_Apr_27_13_35_56_2012_748)--
> > > > Content-Type: Text/Plain; charset=us-ascii
> > > > Content-Transfer-Encoding: 7bit
> > > >
> > > > Rick Mackl
Daniel Braniss wrote:
> > Daniel Braniss wrote:
> > > > Daniel Braniss wrote:
> > > > > > Security_Multipart(Fri_Apr_27_13_35_56_2012_748)--
> > > > > > Content-Type: Text/Plain; charset=us-ascii
> > > > > > Con
Hi All,
I did not see the Intel 82599ES chipset in the hardware release notes
for 8.3 or 9.0. Are these controllers supported at this time?
--
Take care
Rick Miller
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
1, 2012 at 8:36 AM, Rick Miller
> wrote:
>>
>> Hi All,
>>
>> I did not see the Intel 82599ES chipset in the hardware release notes
>> for 8.3 or 9.0. Are these controllers supported at this time?
>>
>> --
>> Take care
>> Rick Miller
>&
unable to verify this, but that's why I was asking for clarification.
I will assume it works at this point.
On Fri, Jun 1, 2012 at 1:25 PM, Michael Butler
wrote:
> On 06/01/12 13:06, Rick Miller wrote:
>> Thanks, Jack!
>>
>> Also another support question for the lists.
don't specify that the BCM5719 is supported, but
the bge manpage appears to indicate it is supported. Is there a
definitive answer whether or not it is supported?
--
Take care
Rick Miller
___
freebsd-stable@freebsd.org mailing list
hanged the Subject line of this email
> in the hope it helps some future soul googling for the answer.
>
> cheers,
> gja
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
yout that they have developed, but it
requires an ODS2 (I think I got that right?) stack and it's unlikely that
the client I am working on will be able to do this any time soon.
rick
> Good pointers, thanks. It's still "appliance", but good to know that
> FreeBSD i
implemented, the NFSv4.1 client
I am working on should be able to use a Lustre server cluster.
So, it could be a while (next summer, maybe?), but that should be FreeBSD
eventually. (I have no idea how easy porting of the Lustre server to FreeBSD
would be?)
Having said the above, I am not familia
On Wed, Jun 13, 2012 at 12:07 PM, Philipp Wuensche wrote:
> Rick Miller wrote:
>> Hi all,
>>
>> I am attempting to build stable/8 (as of 21 May 2012) on a DL360p G8
>> with a BCM5719. I receive a kernel panic very similar to the one at
>> this URL:
>> htt
Hi All,
Wondering if the Intel X520-DA2 10G Fibre NIC is supported in
stable/8. Hardware notes don't specify it, but I have a system up and
the interfaces appear to be loaded by the ix driver. However, status
indicates "no carrier".
--
Take c
On Fri, Jun 22, 2012 at 3:13 PM, Rick Miller wrote:
> Hi All,
>
> Wondering if the Intel X520-DA2 10G Fibre NIC is supported in
> stable/8. Hardware notes don't specify it, but I have a system up and
> the interfaces appear to be loaded by the ix driver. However, status
>
On Fri, Jun 22, 2012 at 3:54 PM, Andrew Boyer wrote:
> The ixgbe driver creates devices named ix0, etc.
>
> I believe you need to run 'ifconfig ix0 up' before it will attempt to get
> link.
Thanks for clarifying that tidbit. At least I know the driver loading
is the correct driver :)
I did try
dmesg and ifconfig output below...
On Fri, Jun 22, 2012 at 4:02 PM, Rick Miller wrote:
> On Fri, Jun 22, 2012 at 3:54 PM, Andrew Boyer wrote:
>> The ixgbe driver creates devices named ix0, etc.
>>
>> I believe you need to run 'ifconfig ix0 up' before it will atte
On Fri, Jun 22, 2012 at 5:21 PM, Jack Vogel wrote:
> Increase your system mbuf pool size, you do not want that failure to happen.
Thanks, Jack. I saw a thread where you discussed this. You are
referring to kern.ipc.nmbclusters, correct?
Should I also adjust the following?
hw.ixgbe.rxd
hw.ixgb
thing looks right from the
host's perspective.
--
Take care
Rick Miller
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Turns out the gbic in the switch was bad...I didn't think there was a
problem on the host, but you all still gave me some good info. I
appreciate it!
On 6/25/12, Rick Miller wrote:
> On Fri, Jun 22, 2012 at 7:23 PM, Jack Vogel wrote:
>> Would probably be good to take car
t initiator credentials from
a keytab entry.)
Hopefully someone else conversant with kerberos can help, rick
> The one where it works on is a Intel based standard workstation (HP
> DC7800). The machine where it does not work is a AMD Opteron based
> server (Sun X4540). Any other kerberos authen
(I'd use
wireshark, since it probably knows a fair bit about Kerberos.)
My guess is that this is what is causing your failure, rick
> The system boots up with em0 as 192.168.1.164 and em1 as
> 192.168.6.2.[2]
> This is the configuration that works, see also the attached tcpdump on
&
Herbert Poeckl wrote:
> On 06/28/2012 02:07 AM, Rick Macklem wrote:
> > The NFS server will authenticate nfs/tmp2.ist.intra against the
> > Kerberos
> > KDC, using the information in the keytab entry. The whole idea
> > behind a
> > host based principal like &q
anyone else has experienced this?
pci4: at device 0.0 (no driver attached)
pci4: at device 0.1 (no driver attached)
--
Take care
Rick Miller
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer wrote:
> On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote:
>> Hi All,
>>
>> I have 2 hosts, HP DL360 G8 and Dell R620. Both have the
>> X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD
&
On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer wrote:
> On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote:
>> Hi All,
>>
>> I have 2 hosts, HP DL360 G8 and Dell R620. Both have the
>> X520-DA2/Intel 82599 10G Fiber NIC. Both also have the same FreeBSD
&
supported.
Maybe the person working on the newer Heimdal can comment?
(I've changed the subject line so they might notice.)
rick
- Original Message -
> Hi,
>
> I have a FreeBSD 9-STABLE acting as a kerberized NFSv3 server.
>
> server# ktutil list
> FILE:/etc/krb5.ke
like that for a long time. I remember running into this way
> back on 6.X and 5.X.
>
> The solution is to:
>
> /tftpboot /vol/tank1 -ro -mapall=nobody
>
Yea, since it doesn't specify any host/network, it is the "def
d
>
>
> Best regards,
>
> --
> Anders.
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
--
Sent from my mobile device
Take care
Rick Miller
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ppens, do a "ps axlH" to see what the nfsd threads are
waiting for. It might give you a hint as to what is happening.
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, se
On Tue, 25 May 2010, Mark Morley wrote:
On Fri, 21 May 2010 11:32:33 -0400 (EDT) Rick Macklem wrote: On Fri, 21 May
2010, Mark Morley wrote:
Having an issue with a file server here (7.3-STABLE i386)
The nfsd processes are hanging. Client access to the nfs shares stops working
and the
On Tue, 25 May 2010, Mark Morley wrote:
On Fri, 21 May 2010 11:32:33 -0400 (EDT) Rick Macklem wrote: On Fri, 21 May
2010, Mark Morley wrote:
Having an issue with a file server here (7.3-STABLE i386)
The nfsd processes are hanging. Client access to the nfs shares stops working
and the
this period.
Any change applied to the aac driver might be a factor, but??
Is anyone else seeing this problem (nfsd threads stuck in wchan "ufs")
on FreeBSD7.3?
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailma
On Sat, 12 Jun 2010, Kostik Belousov wrote:
On Sat, Jun 12, 2010 at 11:56:10AM +0300, Mikolaj Golub wrote:
On Sun, 6 Jun 2010 16:44:43 +0200 Leon Me??ner wrote:
LM> Hi,
LM> I hope this is not the wrong list to ask. Didn't get any answers on
LM> -questions.
LM> When you try to do the fo
x27;d say that having silly rename happen once in a while for unlink when
it doesn't have to happen is better than having the file deleted on the
server while it is still open on the client.
rick
___
freebsd-stable@freebsd.org mailing
On Sun, 13 Jun 2010, Dmitry Pryanishnikov wrote:
Hello!
I'm trying to start the experimental NFSv4 server in RELENG_8 w/o
building it into the kernel, as nfsv4(4) suggests:
... or start mountd(8) and nfsd(8) with the ``-e'' option to force use of the
experimental server. The nfsuserd(8
On Sun, 13 Jun 2010, Kostik Belousov wrote:
My note was not an objection, only a note. Also, when committing, please
add a comment explaining what is going on.
Righto, and my response was just my opinion. I'm assuming Mikolaj is
looking at committing this?
en be used to set boot.netif.gateway to the
correct value for the kernel.
So you might want to check how your dhcpd is configured w.r.t. gateway
address?
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
ke ip helper.
I seen it in cisco routers, not freebsd.
If you haven't been able to get pxeboot to work when the server is on
a different subnet, I'm afraid I can't help with that.
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
1 - 100 of 460 matches
Mail list logo
