[Bug 233401] Is it safe now to use "mount -t nullfs" instead of mount_nullfs in makefiles (does it return non 0 values reliably on errors)?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233401 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added CC||0...@freebsd.org, ||tr...@freebsd.org Status|New |Open --- Comment #1 from Mateusz Piotrowski <0...@freebsd.org> --- trasz@, you've done some work recently on nullfs. Could it be related? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250804] pkg lock -l eroor chmod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250804 Bug ID: 250804 Summary: pkg lock -l eroor chmod Product: Base System Version: 12.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: z462v...@mail.lviv.ua chmod u+s /usr/local/bin/maildrop pkg lock -l Currently locked packages: maildrop-3.0.1 mysql57-client-5.7.31 mysql57-server-5.7.31 pkg upgrade After the update, the rights to the file are passed. wines blocking for changes. fix chmod u+s /usr/local/bin/maildrop -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250804] pkg lock -l eroor chmod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250804 --- Comment #1 from Aleks --- ./postfix reload -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250629] lockups on Dell R740xd with 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250629 --- Comment #3 from Juraj Lutter --- This lockup is *very likely* caused by a faulty SSD attached to LSI card with mrsas driver. After removal of the respective drive, system does not lock up. How could be error reporting and handling improved? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233230] [bhyve] [patch] usage() doesn't list -G debug server option
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233230 --- Comment #4 from Robert Wing --- Thanks for the insight John. Well..looking through the history, it appears bvmdebug was never intended to stick around anyway (as you already know) - so I guess the question is...is now the time to remove it? In r309295 (November 2016), avg notes that bvmdebug/bvmconsole *could* be removed, but that many existing deployments still depend on them. In addition to deferring to Peter, which mailing list (hackers, virtualization, current) should be used to get feedback on whether its time to deprecate bvmdebug and bvmconsole? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250816] AWS EC2 ZFS cannot import its own export!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 Bug ID: 250816 Summary: AWS EC2 ZFS cannot import its own export! Product: Base System Version: 12.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: r...@gusw.net On a fresh deployment of the most recent official FreeBSD-12.2 EC2 AMI on Amazon. No complicated configurations. Only one added line in rc.conf zfs_enable="YES" without which zfs wouldn't even work. The summary overview is this: 1. zpool create works and creates the pool shown with zpool list 2. zpool export ... without error 3. zpool import ... says that one or more devices are corrupt Here is a (ba)sh script, you can just run this yourself: mkdir zfstc truncate -s 100M zfstc/0 truncate -s 100M zfstc/1 mkdir zfstd for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) zpool list zpool export testpool zpool import -d zfstd for i in zfstd/* ; do mdconfig -d -u $(readlink $i) && rm $i ; done rm zfstc/* truncate -s 100M zfstc/0 truncate -s 100M zfstc/1 for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done zpool create testpool raidz $(for i in zfstd/* ; do readlink $i ; done) zpool list zpool export testpool zpool import -d zfstd for i in zfstd/* ; do mdconfig -d -u $(readlink $i) && rm $i ; done rm zfstc/* truncate -s 100M zfstc/0 truncate -s 100M zfstc/1 for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done zpool create testpool mirror $(for i in zfstd/* ; do readlink $i ; done) zpool list zpool export testpool zpool import -d zfstd for i in zfstd/* ; do mdconfig -d -u $(readlink $i) && rm $i ; done rm -r zfstc zfstd You see in it repeated attempts changing the options and zfs device type, none of which makes any difference. Here is the log on another system where it all worked: # mkdir zfstc # truncate -s 100M zfstc/0 # truncate -s 100M zfstc/1 # mkdir zfstd # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done # # zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool 176M 186K 176M- - 1% 0% 1.00x ONLINE - # zpool export testpool # zpool import -d zfstd pool: testpool id: 14400958070908437474 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: testpoolONLINE raidz1-0 ONLINE md10ONLINE md11ONLINE # # for i in zfstd/* ; do mdconfig -d -u $(readlink $i) && rm $i ; done # rm zfstc/* # truncate -s 100M zfstc/0 # truncate -s 100M zfstc/1 # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done # # zpool create testpool raidz $(for i in zfstd/* ; do readlink $i ; done) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool 176M 156K 176M- - 1% 0% 1.00x ONLINE - # zpool export testpool # zpool import -d zfstd pool: testpool id: 7399105644867648490 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: testpoolONLINE raidz1-0 ONLINE md10ONLINE md11ONLINE # # for i in zfstd/* ; do mdconfig -d -u $(readlink $i) && rm $i ; done # rm zfstc/* # truncate -s 100M zfstc/0 # truncate -s 100M zfstc/1 # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done # # zpool create testpool mirror $(for i in zfstd/* ; do readlink $i ; done) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool80M 67.5K 79.9M- - 1% 0% 1.00x ONLINE - # zpool export testpool # zpool import -d zfstd pool: testpool id: 18245765184438368558 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: testpoolONLINE mirror-0 ONLINE md10ONLINE md11ONLINE # # for i in zfstd/* ; do mdconfig -d -u $(readlink $i) && rm $i ; done # rm -r zfstc zfstd Now here on the new system where it fails: [root@geli ~]# mkdir zfstc [root@geli ~]# truncate -s 100M zfstc/0 [root@geli ~]# truncate -s 100M zfstc/1 [root@geli ~]# mkdir zfstd [root@geli ~]# for i in zfstc/* ; do ln -s /dev/$(mdco
[Bug 250816] AWS EC2 ZFS cannot import its own export!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 --- Comment #1 from Gunther Schadow --- Just FYI, not delivering any real news, a forum post where I first reported this and I show proof with the MD5 hashes. https://forums.freebsd.org/threads/zpool-import-unavail-corrupted-data-after-moving-from-an-11-2-to-a-12-2-how-is-this-possible.77560/ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250711] atkbdc: No Keyboard on System76 lemur Pro laptop with 12.1 (11.4 Ok)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250711 --- Comment #12 from Vladimir Kondratyev --- Created attachment 219311 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219311&action=edit atkbdc_quirks.patch Try attached patch (on unmodified sources of 12+ or 13) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667 --- Comment #3 from Seb --- Turns out TrueNAS does not output crash-dumps in the way I was expecting, I've has another 9 kernel panics since my last comment but all produced only text-dumps. I *think* I've got it setup to do a core-dump next crash now using sysctl to override the text-dump pending flag... so hopefully will have a vmcore for you soon. The panic string has been different the last few times: Dump header from device: /dev/ada1p3 Architecture: amd64 Architecture Version: 4 Dump Length: 1751040 Blocksize: 512 Compression: none Dumptime: Sun Nov 1 08:33:26 2020 Hostname: nas.lan Magic: FreeBSD Text Dump Version String: FreeBSD 12.2-RC3 7c4ec6ff02c(HEAD) TRUENAS Panic String: Bad tailq NEXT(0x82134d98->tqh_last) != NULL Dump Parity: 3497888606 Bounds: 3 Dump Status: good Another TrueNAS user is reporting similar issues and believes it may be related to the Intel 10Gb 'ix' drivers. Is that a possibility? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667 --- Comment #4 from Seb --- The message buffer seems to indicate the panic occurs in relation to interface ix1 coming 'up': <6>ix1: link state changed to UP panic: Bad tailq NEXT(0x82135158->tqh_last) != NULL cpuid = 3 time = 1604305215 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0075d697a0 vpanic() at vpanic+0x17b/frame 0xfe0075d697f0 panic() at panic+0x43/frame 0xfe0075d69850 callout_process() at callout_process+0x32f/frame 0xfe0075d698c0 handleevents() at handleevents+0x185/frame 0xfe0075d69900 timercb() at timercb+0x196/frame 0xfe0075d69950 lapic_handle_timer() at lapic_handle_timer+0x9b/frame 0xfe0075d69980 Xtimerint() at Xtimerint+0xb1/frame 0xfe0075d69980 --- interrupt, rip = 0x811af6e6, rsp = 0xfe0075d69a50, rbp = 0xfe0075d69a50 --- acpi_cpu_c1() at acpi_cpu_c1+0x6/frame 0xfe0075d69a50 acpi_cpu_idle() at acpi_cpu_idle+0x232/frame 0xfe0075d69aa0 cpu_idle_acpi() at cpu_idle_acpi+0x3e/frame 0xfe0075d69ac0 cpu_idle() at cpu_idle+0x9f/frame 0xfe0075d69ae0 sched_idletd() at sched_idletd+0x3f1/frame 0xfe0075d69bb0 fork_exit() at fork_exit+0x80/frame 0xfe0075d69bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe0075d69bf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667 --- Comment #5 from Seb --- Created attachment 219312 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219312&action=edit Text Dump 2 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667 --- Comment #6 from Mark Johnston --- (In reply to Seb from comment #4) That may just be the last line printed in a while. I would expect the interfaces to come up during boot, at which point they'll log messages. Indeed, from the second panic it looks like the callout lists are getting corrupted somehow. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250816] AWS EC2 ZFS cannot import its own export!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 --- Comment #2 from Gunther Schadow --- Testing on other FreeBSD EC2 AMIs User data to facilitate the test with less manual work: - #!/bin/sh echo >>/etc/rc.conf echo 'zfs_enable="YES"' >>/etc/rc.,conf - Here is my test protocol login as ec2-user then cut and paste: - su sh uname -a mkdir zfstc truncate -s 100M zfstc/0 truncate -s 100M zfstc/1 mkdir zfstd for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) zpool list zpool export testpool zpool import -d zfstd shutdown -p now - Now the test result: - # uname -a FreeBSD freebsd 11.4-RELEASE-p3 FreeBSD 11.4-RELEASE-p3 #0: Tue Sep 1 08:22:33 UTC 2020 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # mkdir zfstc # truncate -s 100M zfstc/0 # truncate -s 100M zfstc/1 # mkdir zfstd # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done # # zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool 176M 186K 176M- - 1% 0% 1.00x ONLINE - # zpool export testpool # zpool import -d zfstd pool: testpool id: 488462546239790676 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: testpoolONLINE raidz1-0 ONLINE md0 ONLINE md1 ONLINE # # shutdown -p now Shutdown NOW! - Next, is it an issue with FreeBSD-12 in particular? First I will reproduce the problem on a brand new 12.2 again, this time following the exact same protocol that succeeded with 11.4 - ec2-user@freebsd:~ $ su root@freebsd:/home/ec2-user # sh root@freebsd:/home/ec2-user # uname -a FreeBSD freebsd 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC amd64 root@freebsd:/home/ec2-user # mkdir zfstc root@freebsd:/home/ec2-user # truncate -s 100M zfstc/0 root@freebsd:/home/ec2-user # truncate -s 100M zfstc/1 root@freebsd:/home/ec2-user # mkdir zfstd root@freebsd:/home/ec2-user # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done root@freebsd:/home/ec2-user # root@freebsd:/home/ec2-user # zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) root@freebsd:/home/ec2-user # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool 176M 167K 176M- - 1% 0% 1.00x ONLINE - root@freebsd:/home/ec2-user # zpool export testpool root@freebsd:/home/ec2-user # zpool import -d zfstd pool: testpool id: 7726589044207947012 state: UNAVAIL status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: http://illumos.org/msg/ZFS-8000-5E config: testpool UNAVAIL insufficient replicas raidz1-0UNAVAIL insufficient replicas 17541269597952794361 UNAVAIL corrupted data 14116473632156932352 UNAVAIL corrupted data root@freebsd:/home/ec2-user # root@freebsd:/home/ec2-user # shutdown -p now Shutdown NOW! - Let's do the 12.2/ARM, perhaps something was screwed up only on the 12.2 amd64 build - ec2-user@freebsd:~ $ su root@freebsd:/home/ec2-user # sh root@freebsd:/home/ec2-user # uname -a FreeBSD freebsd 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC arm64 root@freebsd:/home/ec2-user # mkdir zfstc root@freebsd:/home/ec2-user # truncate -s 100M zfstc/0 root@freebsd:/home/ec2-user # truncate -s 100M zfstc/1 root@freebsd:/home/ec2-user # mkdir zfstd root@freebsd:/home/ec2-user # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done root@freebsd:/home/ec2-user # root@freebsd:/home/ec2-user # zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) root@freebsd:/home/ec2-user # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool 176M 167K 176M- - 1% 0% 1.0
[Bug 233230] [bhyve] [patch] usage() doesn't list -G debug server option
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233230 --- Comment #5 from Peter Grehan --- It is fine to deprecate these. As John mentioned, there are now much better ways to achieve the same functionality. A short email to the virtualization list should be enough to get confirmation this is ok. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250816] AWS EC2 ZFS cannot import its own export!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 --- Comment #3 from Gunther Schadow --- 12.0-RC3 amd64 works! - $ su root@freebsd:/usr/home/ec2-user # sh # uname -a FreeBSD freebsd 12.0-RC3 FreeBSD 12.0-RC3 r341271 GENERIC amd64 # mkdir zfstc # truncate -s 100M zfstc/0 # truncate -s 100M zfstc/1 # mkdir zfstd # for i in zfstc/* ; do ln -s /dev/$(mdconfig -a -t vnode -f $i) zfstd/$(basename $i) ; done # # zpool create -o feature@embedded_data=enabled -o feature@lz4_compress=enabled -O dedup=on -O compression=lz4 testpool raidz $(for i in zfstd/* ; do readlink $i ; done) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUP HEALTH ALTROOT testpool 176M 174K 176M- - 1% 0% 1.00x ONLINE - # zpool export testpool # zpool import -d zfstd pool: testpool id: 3192103039539057096 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: testpoolONLINE raidz1-0 ONLINE md0 ONLINE md1 ONLINE # # shutdown -p now Shutdown NOW! - So now, I think, I showed you how this might be an issue introduced only through 12.1 and .2 and possibly it is a matter how this EC2 AMI is put together. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250823] i386 linuxulator in jail breaks mount
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250823
Bug ID: 250823
Summary: i386 linuxulator in jail breaks mount
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: m...@russell-allen.com
I'm running
FreeBSD 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 GENERIC amd64
which is hosting a jail called 'j1' running
FreeBSD j1 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 GENERIC i386
Inside the jail, the Centos Linux packages are installed.
A host directory is mounted into the jail:
mount_nullfs /${BASE}/ourself-manager /${BASE}/j1/self
I can use a linux binary to check the mounted directory:
jexec j1 /compat/linux/bin/bash -c "ls /self"
(shows big list of files)
However if I attempt to mkdir /self within a linux app, instead of returning
EEXIST it breaks the mount:
jexec j1 /compat/linux/bin/bash -c "mkdir /self"
jexec j1 /compat/linux/bin/bash -c "ls /self"
(shows empty directory)
Once this has happened, no linux app within the jail can see the contents of
/self, nor can freebsd apps started by a linux app. However jailed freebsd apps
started from outside still work, ie
jexec j1 /usr/local/bin/bash -c "ls /self"
(shows big list of files)
If I set enforce_statfs = 0; in my jail.conf, calling mount within the jail
shows /self as still being mounted.
This also occurs where /self is a mounted ZFS dataset instead of a null_fs
mount, and it isn't bash specific - any linux app seems to have the same
result.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250823] i386 linuxulator in jail breaks mount
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250823 Li-Wen Hsu changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org CC||lw...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250816] On 12.1 & 12.2 AWS EC2, ZFS cannot import its own export!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 Gunther Schadow changed: What|Removed |Added Summary|AWS EC2 ZFS cannot import |On 12.1 & 12.2 AWS EC2, ZFS |its own export! |cannot import its own ||export! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250816] ZFS cannot import its own export on AWS EC2 12.1 & 12.2-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 Gunther Schadow changed: What|Removed |Added Summary|On 12.1 & 12.2 AWS EC2, ZFS |ZFS cannot import its own |cannot import its own |export on AWS EC2 12.1 & |export! |12.2-RELEASE -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250816] ZFS cannot import its own export on AWS EC2 12.1 & 12.2-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816 Gunther Schadow changed: What|Removed |Added Severity|Affects Some People |Affects Many People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250804] pkg lock -l eroor chmod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250804 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 178359] [geom] [patch] geom_eli: support external metadata
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=178359 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org Assignee|b...@freebsd.org|g...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
