Re: Problems with em0 driver after upgrade to r303832

[Doug Hardie]

> On 9 August 2016, at 04:40, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> I upgraded my local machine to the above revision a few days ago. Since then 
>> I have seen the local em0 card locking up and getting he following
>> messages in dmesg
>> 
>> em0: Watchdog timeout -- resetting
>> em0: link state changed to DOWN
>> em0: link state changed to UP
>> 
>> 
>> I thought it was the physical card, but I have swapped this out
>> for a completely different one and the problems remain.
> 
> What does pciconf -lvb display for the PCI IDs for this card ?
> 
> If you use r303832, this is CURRENT (12.x) ? Then maybe the
> question should be discussed on curr...@freebsd.org.


I am seeing this on 11.0-BETA3/4.

bge0@pci0:3:0:0:class=0x02 card=0x168614e4 chip=0x168614e4 rev=0x01 
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM57766 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet
bar   [10] = type Prefetchable Memory, range 64, base 0xa070, size 
65536, enabled
bar   [18] = type Prefetchable Memory, range 64, base 0xa071, size 
65536, enabled

It does not occur on another machine with:

bge0@pci0:2:0:0:class=0x02 card=0x16b414e4 chip=0x16b414e4 rev=0x10 
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM57765 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet
bar   [10] = type Prefetchable Memory, range 64, base 0x9040, size 
65536, enabled
bar   [18] = type Prefetchable Memory, range 64, base 0x9041, size 
65536, enabled

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[George Mitchell]

Will someone PLEASE remove freebsd-stable from the CC list of this
ticket?  Thank you. -- George

On 08/09/16 19:10, bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491
> 
> Ngie Cooper  changed:
> 
>What|Removed |Added
> 
>  CC|freebsd-b...@freebsd.org,   |n...@freebsd.org
>|freebsd-stable@FreeBSD.org  |
>Severity|Affects Many People |Affects Some People
> 
> --- Comment #13 from Ngie Cooper  ---
> Please don't add -current or -stable to bugs like this; it spams the list
> unnecessarily (this issue impacts users of iSCSI + ZFS -- which seems a bit
> niche right now)
> 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

Ngie Cooper  changed:

   What|Removed |Added

 CC|freebsd-b...@freebsd.org,   |n...@freebsd.org
   |freebsd-stable@FreeBSD.org  |
   Severity|Affects Many People |Affects Some People

--- Comment #13 from Ngie Cooper  ---
Please don't add -current or -stable to bugs like this; it spams the list
unnecessarily (this issue impacts users of iSCSI + ZFS -- which seems a bit
niche right now)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #12 from Eric van Gyzen  ---
I just reproduced this on 12-CURRENT r303626.  I'm now updating that machine to
the latest head.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #11 from Eric van Gyzen  ---
I just reproduced this on 10.3-STABLE r303633.  I'll try to reproduce on
10.3-RELEASE to see if it would be a new regression in 11.0-RELEASE.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

Xin LI  changed:

   What|Removed |Added

 CC||delp...@freebsd.org
   Assignee|freebsd-b...@freebsd.org|freebsd...@freebsd.org
   Severity|Affects Some People |Affects Many People

--- Comment #10 from Xin LI  ---
I noticed this too but not 100% reproducible.

I don't have iSCSI setup, but do have zvol.  It was a fresh -CURRENT.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

Eric van Gyzen  changed:

   What|Removed |Added

   Hardware|amd64   |Any

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

Eric van Gyzen  changed:

   What|Removed |Added

Summary|System hangs after "Uptime" |System hangs after "Uptime"
   |on reboot   |on reboot with iSCSI, zfs,
   ||and altroot

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #9 from Eric van Gyzen  ---
Steps to reproduce on a stable/11 r303878 GENERIC kernel (and many earlier
revs):

1. Attach to an iSCSI LUN with /etc/iscsi.conf and iscsid.
2. Create a ZFS pool on that LUN:  zpool create iscsi_test da0
3. Export the pool:  zpool export iscsi_test
4. Import the pool with an altroot: zpool import -R /blah iscsi_test
5. shutdown -r now

The system will hang after printing Uptime: XdYmZs.

iSCSI and altroot are key to producing the hang.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #8 from Eric van Gyzen  ---
The debugging kernel options are not part of the problem.  I removed them and
still reproduced the hang.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #7 from Eric van Gyzen  ---
So far, I've been importing the volume using the iSCSI initiator in a bhyve
guest.  To determine whether iSCSI is really involved, I reconfigured to import
the volume onto the bhyve host and pass it to the VM as a virtio block device. 
I failed to reproduce the hang.  (I'm still importing with altroot.)

Also, I have only reproduced the hang on systems with debugging kernel options
such as INVARIANTS and WITNESS.  To determine whether they're really involved,
I'm rebuilding my VM's kernel without these options.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #6 from Eric van Gyzen  ---
One of those systems is a bhyve VM.  On the host, I see that all CPU threads
are "vmidle" and consuming no CPU time, so they're blocked on some event, not
spinning.  (I realize this doesn't help much.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #5 from Eric van Gyzen  ---
As an amendment to my last comment, the zpool has to be imported with altroot:

zpool import -R /foo bar_pool

I was failing to reproduce this on two other systems by having the pool
imported without -R (altroot).  When I added the altroot, those two systems
began reproducing it consistenly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

--- Comment #4 from Eric van Gyzen  ---
I think I've narrowed it down to having a ZFS pool imported from an iSCSI LUN
using the in-kernel software initiator.

g_amanakis:  Is this true on your system, too?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

Kubilay Kocak  changed:

   What|Removed |Added

 CC|freebsd-am...@freebsd.org   |r...@freebsd.org
  Flags||mfc-stable10?,
   ||mfc-stable11?
   Keywords||needs-qa
 Status|New |Open

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

Eric van Gyzen  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People
 CC||vangy...@freebsd.org

--- Comment #3 from Eric van Gyzen  ---
I have also seen this on a Dell Precision Workstation running 11-CURRENT.  It
doesn't always happen, but it seems more likely after a
buildworld/installworld.  I'm using ZFS on a single SSD and an iSCSI LUN using
the in-kernel initiator.  I'm also using the nvidia driver, since this is my
main desktop.

I'll try to reproduce and get more details (i.e. a core dump).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 211491] System hangs after "Uptime" on reboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491

g_amana...@yahoo.com changed:

   What|Removed |Added

 CC||freebsd-b...@freebsd.org,
   ||freebsd-stable@FreeBSD.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Tomoaki AOKI]

Hi

Unfortunately, the revision shown by `uname -a` etc. is NOT the actual
newest revision of the branch, because the set of revision numbers is
exactly the same throuout every branches.

# It relies on when he / she `svn(lite) up`'ed and gets newest rev.
 

So the easiest way to determine the actual revision is, for this case,
to look into the pipermail archive of freebsd-src-stable10 and look for
the maximum nunber NOT EXCEEDING the revision shown.

This case, the actual revision Pete has should be r303827.

On Tue, 9 Aug 2016 13:40:23 +0200
Kurt Jaeger  wrote:

> Hi!
> 
> > I upgraded my local machine to the above revision a few days ago. Since 
> > then I have seen the local em0 card locking up and getting he following
> > messages in dmesg
> > 
> > em0: Watchdog timeout -- resetting
> > em0: link state changed to DOWN
> > em0: link state changed to UP
> > 
> > 
> > I thought it was the physical card, but I have swapped this out
> > for a completely different one and the problems remain.
> 
> What does pciconf -lvb display for the PCI IDs for this card ?
> 
> If you use r303832, this is CURRENT (12.x) ? Then maybe the
> question should be discussed on curr...@freebsd.org.
> 
> -- 
> p...@opsec.eu+49 171 3101372 4 years to 
> go !
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 


-- 
Tomoaki AOKI
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Pete French]

> > I thought it was the physical card, but I have swapped this out
> > for a completely different one and the problems remain.
>
> What does pciconf -lvb display for the PCI IDs for this card ?

I have just dropped a third card into the machine 9I need
to get some work done unfortnately) - for this the output is 

em0@pci0:3:2:0: class=0x02 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '82541PI Gigabit Ethernet Controller'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xfebc, size 131072, enabled
bar   [14] = type Memory, range 32, base 0xfeba, size 131072, enabled
bar   [18] = type I/O Port, range 32, base 0xe400, size 64, enabled

I will let you know if it locks up, or if it doesnt -I swapped
PCI slots as well in case this is actually a hardware issue.

> If you use r303832, this is CURRENT (12.x) ? Then maybe the
> question should be discussed on curr...@freebsd.org.

Its 10.3-STABLE according to uname -a

-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Kurt Jaeger]

Hi!

> I upgraded my local machine to the above revision a few days ago. Since then 
> I have seen the local em0 card locking up and getting he following
> messages in dmesg
> 
> em0: Watchdog timeout -- resetting
> em0: link state changed to DOWN
> em0: link state changed to UP
> 
> 
> I thought it was the physical card, but I have swapped this out
> for a completely different one and the problems remain.

What does pciconf -lvb display for the PCI IDs for this card ?

If you use r303832, this is CURRENT (12.x) ? Then maybe the
question should be discussed on curr...@freebsd.org.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Jenkins build is still unstable: FreeBSD_stable_10 #356

[George Mitchell]

On 08/09/16 05:10, Craig Rodrigues wrote:
> 
> 
> On Mon, Aug 8, 2016 at 4:26 PM, George Mitchell  > wrote:
> [...]
> Can someone please clarify for me the distinction between
> succeeding vs. failing and being stable vs. unstable?   -- George
> 
> 
> Unstable means the build succeeded, but one of the tests is failing.
> [...]

Thanks for the explanation!-- George

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problems with em0 driver after upgrade to r303832

[Pete French]

I upgraded my local machine to the above revision a few days ago. Since then I 
have seen the local em0 card locking up and getting he following
messages in dmesg

em0: Watchdog timeout -- resetting
em0: link state changed to DOWN
em0: link state changed to UP


I thought it was the physical card, but I have swapped this out
for a completely different one and the problems remain. Am am concerned
as we run a lot of em0 cards in production and started upgrading those too,
as I had not associated the problem with the software upgrade until just now.

Any siggestions ? Am reluctant to start rolling this back, and it is
only showing up on one machine for now - is anyone else seeing this ?

-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

[Harry Schmalzbauer]

Bezüglich Mark Johnston's Nachricht vom 09.08.2016 08:02 (localtime):
…
>>
>> Just for anybody else needing unionfs:
>> https://people.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch
>>
>> This patch still applies and I'm successfully using this (unmodified) up
>> to FreeBSD-10.3 and never had any panic in all these years.
> 
> Having spent some time looking at unionfs, I'm a bit skeptical that this
> patch will address the panic you reported earlier, though I'd be
> interested to know if it does. 

Thanks for your attention.
I can confirm that it has prevented panics for more than 4 years
(9.0-10.3) and it seems to be still "good enough" to also prevent panics
in 11-BETA4.
I updated my build host (stable/11, this time with the
unionfs_missing_insmntque_lock.patch), where the recent panics happened
and unionfs gets much more utilized than usually in my setups: No panic
with that patch anymore.
Just one message like "prevented resource deadlock" occured.

> Reading the code, I think it will just
> address an INVARIANTS-only assertion in insmntque1().
> 
> Unfortunately, unionfs is quite difficult to fix within the current
> constraints of FreeBSD's VFS. unionfs_readdir() is a particularly good
> demonstration of this fact: some callers of VOP_READDIR expect the
> cookies returned by the FS to be monotonically increasing, but unionfs
> has no straightforward way to make this guarantee.

I'm sorry, I can't provide help here. My skills would require a huge
ammount of lerning-time to get into that matter. I'd love to do that,
but I can't afford :-(

Thanks,

-Harry
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Jenkins build is still unstable: FreeBSD_stable_10 #358

[Randy Bush]

jenkins-ad...@freebsd.org wrote:
> 
> See 
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

procmail time
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Jenkins build is still unstable: FreeBSD_stable_10 #356

[Craig Rodrigues]

On Mon, Aug 8, 2016 at 4:26 PM, George Mitchell 
wrote:

> On 08/08/16 18:56, jenkins-ad...@freebsd.org wrote:
> > See 
> > [...]
>
> Can someone please clarify for me the distinction between
> succeeding vs. failing and being stable vs. unstable?   -- George
>
>
Unstable means the build succeeded, but one of the tests is failing.

Look at the bottom of https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/356/
to see which test is failing.

It would be nice if someone could fix this, since it seems to be a
legitimate bug that has
been introduced by recent merges.

--
Craig
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c

[Harry Schmalzbauer]

Bezüglich Kurt Jaeger's Nachricht vom 09.08.2016 07:32 (localtime):
> Hi!
> 
>> Since then I'm draging a minimal patch which prevents at least the
>> kernel panics for me.
>> Unfortunately I don't have the skills to continue Attilio Raos work.
>>
>> Just for anybody else needing unionfs:
>> https://people.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch
> 
> Is this referenced in any PR ? If not, can you create one ?

Good question, bad answer: No
I had been told not to file a PR at that time because unionfs overhaul
was planned/needed. Partial fixes would have been counterproductive in
that state and not "the right way to go".
Looks like overhaul hasn't really happened during the last 4 years and
since I was happy with the partial patch, I haven't followed unionfs
development.
In the mean time I remember that lots of fs-stress-tests were added to
the FreeBSD test suite, but I'm not familar with a single one, even not
with ATF and the like, and won't find the time to dig into them.
So presently I hesitate picking up that old issue and file a PR, because
developers resources are extremely limited regarding unionfs, and the PR
should be attended by someone who has time and knowledge to make
developers life easier by providing qualified analysis and tests. All I
could do at the moment is to point at a dysfunction, which is documented
in the man page, which isn't really helpful/needed.


>> First thing to do for me, after I won in lottery, was to find someone
>> who can be sponsored fixing unionfs ;-) And bringing MNAMELEN into 21st
>> century state, matching ZFS needs:
>> https://lists.freebsd.org/pipermail/freebsd-hackers/2015-November/048640.html
>> This is another patch I'm carrying for a very long time which solves
>> tremendous limitations for me. Without that, I couldn't use ZFS
>> snapshots in real world, along with a human-friendly dataset naming :-)
> 
> And is there a PR for that ?

Sadly, the same answer with similar reasons is true.
I asked Doug Ambrisko (the author of the mount_bigger_2_1.patch) at
10.2-BETA time (2015/07/10) about progress and future handling of his patch.
He answered that Marshal Kirk McKusik asked him not to continue in that
direction, since »it would make the 64 bit inode work harder«.

So we agreed continuing being happy with the patch in our world, leaving
the rest unhappy ;-) See the link to that discussion above.

I was kind of astonsihed that this patch still applies to 11 and it
seems 11 still has the MNAMELEN limitation besides make_dev_p() ability
to handle extended lengths.

CC'ed Doug, perhaps he joins this thread calrifying things.

The unionfs thing is a edge-case thing, but MNAMELEN is much more
important, imho, since ZFS is one of FreeBSD's most appreciated "new
features" and this MNAMELEN limit needlessly counteracts ZFS' deployment.

Of course I'll keep nagging from time to time ;-) And file PRs if not
told otherwise :-)

-Harry
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_stable_10 #358

[jenkins-admin]

See 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"