[Bug 240158] utimensat system call (and C API) should allow more than 2 timestamps, to simplify changing birth time
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240158 Bug ID: 240158 Summary: utimensat system call (and C API) should allow more than 2 timestamps, to simplify changing birth time Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: s...@rogue-research.com The utimensat() man page says: "To set both a birth time and a modification time, two calls are required; the first to set the birth time and the second to set the (presumably newer) modification time. Ideally a new system call will be added that allows the setting of all three times at once." Such a newer system call would indeed simplify changing the birthtime of a file, which currently is rather complicated to edit. I can't find any existing bug for this, so thought I'd create one... -- 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 240157] cp has no ability to preserve extended attributes when copying a file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240157 Conrad Meyer changed: What|Removed |Added URL||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2401 ||46 --- Comment #1 from Conrad Meyer --- We don't have a good "Related" bug field and 240146 doesn't have a blocking relationship with this one, so I just stuck it in the URL field for easier lookup. -- 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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 --- Comment #6 from Conrad Meyer --- (In reply to Sean McBride from comment #4) On Windows, they're called "ADS" (alternative data streams) and the semantics are somewhat different, but they tend to be used in similar ways as extattrs. > but I'd like *some* option for cp to preserve them. :) Me too :-). > For cp itself, I created ... Thanks! -- 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 240157] cp has no ability to preserve extended attributes when copying a file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240157 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Status|New |Open -- 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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 --- Comment #5 from Sean McBride --- For cp itself, I created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240157 -- 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 240157] cp has no ability to preserve extended attributes when copying a file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240157 Bug ID: 240157 Summary: cp has no ability to preserve extended attributes when copying a file Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: s...@rogue-research.com I was very surprised to see that neither 'cp -p' nor 'cp -a' preserve the extended attributes of a file. example: root@freenas[/test]# lsextattr user A.txt A.txt DosStream.com.apple.TextEncoding:$DATA DosStream.AFP_Resource:$DATA DosStream.AFP_AfpInfo:$DATA DOSATTRIB DosStream.com.apple.lastuseddate#PS:$DATA root@freenas[/test]# cp -a A.txt A2.txt root@freenas[/test]# lsextattr user A2.txt A2.txt EAs sometimes contain important data, and there should surely be some kind of option to preserve them when copying a file. In contrast, macOS's cp -p does preserve EAs. See also #240146 for related bug against the cp man page for saying nothing. -- 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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 --- Comment #4 from Sean McBride --- Not sure about Windows, but EAs are quite common on macOS. Re: -p vs -a, don't much care myself, but I'd like *some* option for cp to preserve them. :) -- 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 240156] Remove flags argument from VOP_UNLOCK
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240156 Bug ID: 240156 Summary: Remove flags argument from VOP_UNLOCK Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: m...@freebsd.org Flags: exp-run? See https://reviews.freebsd.org/D21427 The diff is 160KB in size so I'm not attaching it, you can find it here: https://people.freebsd.org/~mjg/vop_unlock_complete3.diff There may be kernel modules failing. The patch applies cleanly on top of r351556. -- 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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 --- Comment #3 from Conrad Meyer --- My impression is that extattr/fork use is much less common in BSD/Linux than Windows. It seems like Mac gained support in 10.4 in ~2005. It's quite possible that folks who ran into this shortcoming just installed coreutils and used gcp. Btw, I don't think the cp(1) -p behavior is wrong here. I was suggesting adding extattr support to '-a', like GNU cp does. -- 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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 --- Comment #2 from Sean McBride --- I'm happy to file an additional bug against 'cp -p' behaviour. I tried to search for an existing one, but didn't find it. Surely I can't be the first to notice/want this? -- 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 239894] security.bsd.stack_guard_page default causes Java to crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894 --- Comment #15 from Greg Lewis --- Hi Konstantin, It looks like you have been working on the procctl approach based on https://reviews.freebsd.org/D21352. Thanks for doing that! A couple of questions/comments though. Can we help test this approach? I.e., verify that fixes the problem for the JDK? I'm happy to compile a kernel with the changes and see if that resolves the issue if that would help. A concern though is that this doesn't address the other problems outside of the JDK that have been raised in this thread. Those are the issues raced by Kurt and Shawn in the comments here including problems with some values of this sysctl making the system unstable or unusable, whether it should be placing pages within the stack at all, and whether stable values (i.e., 0 or 1) actually prevent the stack clash issues at all. Do you see what you're doing as a stop gap prior to longer term work here? -- 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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Status|New |Open --- Comment #1 from Conrad Meyer --- Yeah, it's unfortunate! Totally agree we should at a minimum document the gap. cp(1) is an old tool and long predates extended attributes in FreeBSD. FWIW, POSIX 1003.1-2017 cp(1) also does not mention extattrs at all: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/cp.html GNU cp only touches on it obliquely: http://man7.org/linux/man-pages/man1/cp.1.html > -a, --archive > same as -dR --preserve=all ... > -p same as --preserve=mode,ownership,timestamps > > --preserve[=ATTR_LIST] > preserve the specified attributes (default: > mode,ownership,timestamps), if possible additional attributes: > context, links, xattr, all ^ (And note that even GNU cp's bare '-p' option does NOT preserve extattrs; you need to pass '-a'.) So this is a valid doc bug, but could also be filed as a Base system / bin bug to add the missing support. As a workaround, tar(1) can be used to copy extended attributes (--xattrs). -- 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 240134] zfs: Kernel panic while importing zpool (blkptr at has invalid COMPRESS 127)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240134 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@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 240145] [zfs] kernel panic with hanging vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240145 Mark Linimon changed: What|Removed |Added Keywords||panic Assignee|b...@freebsd.org|f...@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 240146] 'man cp' does not discuss extended attributes; it really should since even -p discards them!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240146 Bug ID: 240146 Summary: 'man cp' does not discuss extended attributes; it really should since even -p discards them! Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: s...@rogue-research.com CC: d...@freebsd.org The man page for 'cp' does not contain the word "extended" nor "attribute". I was very surprised to see that even 'cp -p' apparently does not preserve the extended attributes of a file. I'd argue 'cp -p' behaviour is wrong, but at the very least it should be documented. By contrast, the macOS 10.13 man page says: "-pCause cp to preserve the following attributes of each source file in the copy: modification time, access time, file flags, file mode, user ID, and group ID, as allowed by permissions. Access Control Lists (ACLs) and Extended Attributes (EAs), including resource forks, will also be preserved." A simple sentence to warn that cp -p will blow away EAs would help. We're talking about data loss here. :( example: root@freenas[/test]# lsextattr user A.txt A.txt DosStream.com.apple.TextEncoding:$DATA DosStream.AFP_Resource:$DATA DosStream.AFP_AfpInfo:$DATA DOSATTRIB DosStream.com.apple.lastuseddate#PS:$DATA root@freenas[/test]# cp -a A.txt A2.txt root@freenas[/test]# lsextattr user A2.txt A2.txt -- 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 240145] [zfs] kernel panic with hanging vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240145 rai...@ultra-secure.de changed: What|Removed |Added Summary|kernel panic with hanging |[zfs] kernel panic with |vdev|hanging vdev -- 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 240145] kernel panic with hanging vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240145 Bug ID: 240145 Summary: kernel panic with hanging vdev Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: rai...@ultra-secure.de Hi, I get kernel panics like this one: 2019-08-27T09:51:47+02:00 server-log03-prod kernel: <118>[51] 2019-08-27T09:51:47+02:00 server-log03-prod 1 2019-08-27T09:51:47.264114+02:00 server-log03-prod savecore 75563 - - reboot after panic: I/O to pool 'datapool' appears to be hung on vdev guid 3442909230652761189 at '/dev/da0'. dmesg shows: [167] [ERROR]::[17:655.0][0,84,0][CPU 7][pqi_map_request][540]:bus_dmamap_load_ccb failed = 36 count = 131072 [167] [WARN]:[17:655.0][CPU 7][pqisrc_io_start][794]:In Progress on 84 [167] Assertion failed at file /usr/src/sys/dev/smartpqi/smartpqi_response.c line 203 before it crashes. There's a scrub running and I would assume that it's triggered by that. The hardware is a HP DL380 Gen10 with 2*8 disk RAIDz2, booting from a separate controller. zpool status pool: datapool state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub in progress since Tue Aug 27 03:49:26 2019 596G scanned at 832M/s, 429M issued at 599K/s, 14.6T total 0 repaired, 0.00% done, no estimated completion time config: NAMESTATE READ WRITE CKSUM datapoolONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 da3 ONLINE 0 0 0 da2 ONLINE 0 0 0 da1 ONLINE 0 0 0 da0 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 raidz2-1 ONLINE 0 0 0 da11ONLINE 0 0 0 da10ONLINE 0 0 0 da9 ONLINE 0 0 0 da8 ONLINE 0 0 0 da12ONLINE 0 0 0 da13ONLINE 0 0 0 da14ONLINE 0 0 0 da15ONLINE 0 0 0 raidz2-2 ONLINE 0 0 0 da16ONLINE 0 0 0 da17ONLINE 0 0 0 da18ONLINE 0 0 0 da19ONLINE 0 0 0 da20ONLINE 0 0 0 da21ONLINE 0 0 0 da22ONLINE 0 0 0 da23ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da24p4 ONLINE 0 0 0 da25p4 ONLINE 0 0 0 errors: No known data errors datapool is on a HPE E208i-p SR Gen10 1.98 zroot is on a HPE P408i-a SR Gen10 1.98 I've updated all the firmware to what is available in SPP 2019.03.01 I might be a hardware-issue, but I'm not really sure where to put it. Is it da0? What do these error-messages mean? -- 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"
