On 10/05/2012 05:40 AM, Konstantin Belousov wrote:
This is the whole difference between stable and HEAD nullfs.
Retest the HEAD then.
Can't reproduce it with HEAD (FreeBSD freebsd-tower.goebo.site
10.0-CURRENT FreeBSD 10.0-CURRENT #0 r241218: Fri Oct 5 08:26:17 CEST
2012
I exported the NFSv4 shares via nullfs, booted the 10.0-CURRENT kernel
and the machine does not crash. Running 9.1-PRERELEASE, it still crashes
(as it should ;).
I just applied the numeric-uidgid patch to CURRENT (worked so far) and
compile the kernel with the patch and try it another time, just
On 10/04/2012 08:41 AM, Norbert Aschendorff wrote:
I just applied the numeric-uidgid patch to CURRENT (worked so far) and
compile the kernel with the patch and try it another time, just to
eliminate the possibility of a bug in this patch (the machine never
crashed before using this patch
Hehe, sure, if you assist me :)
I'm not very experienced with SVN, I'm actually a git user and I think
it's also better if I do /not/ express my opinion on SVN here ;)
The only actions I'm currently able to do in SVN are checkout, update,
commit and view log and status -- so any help is
Does not compile: http://nopaste.info/2bc2c189eb.html (I also #define-d
a constant, but that works)
--Norbert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On 10/04/2012 12:45 PM, Konstantin Belousov wrote:
But the errors has nothing to do with my nullfs backport.
You're right; they stem from Rick's patch (from line 207 in
numeric-uidgid.patch on):
-nd-nd_repstat = nfsv4_strtogid(cp,j,gid,p);
+nd-nd_repstat = nfsv4_strtogid(nd, cp, j, gid,
+ p);
On 10/04/2012 01:53 PM, Rick Macklem wrote:
Looks like you missed the change to fs/nfs/nfs_var.h, which changes
the prototypes for nfsv4_strtouid() and nfsv4_strtogid().
I see the problem, but I don't really understand why it failed. I
applied the whole patch...
However, 9.1-PRERELEASE is
Nop, the patch doesn't seem to work - the machine crashes again. :|
Norbert
___
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 10/02/2012 11:15 PM, John Baldwin wrote:
You could try adding a different WITNESS check (using WITNESS_WARN) to see
which NFS proc returns with a lock held so you can catch this when it first
occurs rather than much later after the fact. Do you have the start of the
log messages?
Yep, I
On 10/03/2012 09:21 AM, Norbert Aschendorff wrote:
So I just have to compile a kernel including option WITNESS_WARN and
Well, obviously doesn't work, so only WITNESS_SKIPSPIN...
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
Another logs - even with a /var/crash crash report :)
Please note: The /var/crash files stem from another crash than the big
syslog does!
The syslog file inside the tarball is about 4.7 MB; it contains
everything since the start of the crash.
New /var/crash files:
On 10/03/2012 05:54 PM, Konstantin Belousov wrote:
So do you use nullfs exported mounts ? And stable ?
Can you try to remove nullfs from the set up ?
Yes, I am using nullfs for the exports (mounting the exported
directories to subdirectories of /srv). In the FreeBSD man pages and the
On 10/03/2012 07:39 PM, Konstantin Belousov wrote:
Can you try HEAD kernel ?
Theoretically, yes. But it's a network machine, so... if something goes
wrong, it'd be rather bad :| And I'm afraid of HEAD ;)
I'll try it nevertheless... Fortunately, I even have ScreenKeyboard at
the machine (if
I'll compile a kernel with
options WITNESS
options WITNESS_KDB
ok? Or should I include WITNESS_SKIPSPIN too?
Regards,
Norbert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
Well...
Here the results for a kernel without WITNESS_SKIPSPIN (I'll compile one
including that tomorrow, but until then...)
Good news is: The kernel crashed with activated WITNESS.
Bad news is: I have to turn power off after the crash with WITNESS. The
crash dump is _not_ written to disk :(
On 10/01/2012 02:07 PM, Rick Macklem wrote:
Is the NFS client using Kerberos or AUTH_SYS for the mount? (And if you
are using Kerberos, have you tried the rsync with an AUTH_SYS mount?)
No, it's not using Kerberos. Only network-based access control or
however it's called (restricted via client
Hi,
my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site
9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01
CEST 2012 l...@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC
i386) crashes reproducibly when rsync-ing files to an NFSv4 share on
the FreeBSD
Hey,
I downloaded FreeBSD-STABLE source via SVN and I'm now at r241038 from
2012-09-28 22:29:06 +0200 (Fri, 28 Sep 2012).
If I want to build world (make buildworld), I get the following errors:
http://pastebin.com/raw.php?i=Yrs8JSwg
I've set the CC and CXX variables in make.conf to gcc
On 09/29/2012 04:09 PM, David Wolfskill wrote:
On Sat, Sep 29, 2012 at 12:29:26PM +0200, Norbert Aschendorff wrote:
Hey,
I downloaded FreeBSD-STABLE source via SVN and I'm now at r241038 from
2012-09-28 22:29:06 +0200 (Fri, 28 Sep 2012).
On which branch? (stable/7, stable/8, and stable/9
Seems to help, thank you :)
But what exactly messed it up? Do you have an idea?
--Norbert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On 09/29/2012 04:55 PM, Dimitry Andric wrote:
On 2012-09-29 16:16, Norbert Aschendorff wrote:
...
src.conf does not exist here, and make.conf contains this:
# added by use.perl 2012-08-23 17:45:18
PERL_VERSION=5.14.2
CFLAGS=-pipe
#CC=clang
#CC=gcc
CXXFLAGS=-pipe
#CXX=clang++
#CXX=g
I tested it using tcpdump: http://nopaste.info/9394068f54_nl.html
The length field says for each packet 1408 bytes, so that should be OK.
The Wireshark instance on the iperf server says something like 16732
bytes on wire for the most packets (not always with 16732 bytes, but
most packets over
That's a bit difficult because I own only one FreeBSD machine - to
provide a result FreeBSD-FreeBSD I'd have to set up a completely new
system. On the other side, I could try it using the Live system. I'll
try it and tell you when I have results.
Norbert
So, I got the results using the Live system.
Machine [1] is an older Thinkpad T61 (running the Live system), Machine
[2] the well-known FreeBSD machine from the previous benchmark. Both
machines run FreeBSD 9.1-RC1 GENERIC.
{Values in MBit/s}
Configuration IPv6IPv4
Hi,
I'm using here a Gigabit Ethernet network and some UN*X machines, among
others some Linux-based (Kernel 3.x) and one running FreeBSD 9.1-RC1.
Using iperf (in TCP mode), the IPv6 bandwith between two Linux machines
(directly attached to the same switch) is about 925 Mbit/s, IPv4
bandwith is
I already had a problem with this, but this is fixed: 1. The hostnames
are correct 2. in the debian /etc/idmapd.conf, the right domain name is
specified 3. The names are transmitted correctly -- tested with
Wireshark. If the problem was wrong domain names, I had found it because
I always take a
Sorry, I was wrong :|. This time, the packets contain the numeric user
and group IDs (in my case, 1000:1000). A pcap file with some NFS
requests and responses can be found here:
http://lbo.spheniscida.de/Files/nfs.pcap -- sorry for that
misinformation in the previous mail :(
Norbert
It looks as if the problem is related to this bug which shows the
exactly same symptoms (if you look at the package dumps). It's also
Kernel 3.3 with which it also begun here. And with kernel 3.1, it works
(same here).
-- https://bugzilla.novell.com/show_bug.cgi?id=756897
I don't know what's the
And just another thing: Using the Fedora machine (also kernel 3.5) as
server, I see the exactly same behavior. Sending '1000' (numeric UID)
instead of actual username. Using Kernel 3.2 on the server, the
translation even works when using the same username and different IDs
(as it should...).
As this is obviously a Linux (kernel(?)) problem, I think I can close
this thread. And thank you for your answers, Rick :)
Norbert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
Hi all,
I recently noticed a problem in my network. I use some desktop machines
there, two with Linux kernel (Debian and Fedora, both using Kernel 3.5)
and a FreeBSD 9.0 (p4) machine.
Some days ago, I updated the Debian machine from Kernel 3.2 to Kernel
3.5 (from the experimental branch,
31 matches
Mail list logo
