Same issue as reported here: https://github.com/openzfs/zfs/issues/10522
** Also affects: zfs via
https://github.com/openzfs/zfs/issues/10522
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
So it may be that the write-back-throttling (wbt) for the underlying
devices is getting confused about the exact throttle rates are for these
devices and somehow getting stuck. It maybe worth experimenting by
disabling the throttling and seeing if this gets I/O working again.
For example, to disa
It may also be a good idea to disable any power management on USB too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1899249
Title:
OpenZFS writing stalls, under load
Status in Nat
That's great news. Let's keep this bug open for the moment as
"incomplete" and if you don't report back after ~6 weeks or so it will
automatically be closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs
of ZFS mount
options)
** Affects: zfs-linux (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin I
That warning message is from the Raspberry Pi firmware broadcom
get_property sys interface, some user space program has read an old
deprecated sys interface and is just warning to use the hwmon sysfs
interface and it has no bearing on the ZFS or block WBT settings.
--
You received this bug notifi
So it may be that the write-back-throttling (wbt) for the underlying
devices is getting confused about the exact throttle rates are for these
devices and somehow getting stuck. It maybe worth experimenting by
disabling the throttling and seeing if this gets I/O working again.
For example, to disab
The comment #4 has not been responded to for 6 weeks, so this bug will
be closed as Won't Fix as it inactive. If this is still and issue,
please re-open this bug and we can continue to try to work on this
issue.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You rece
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I think this may be a race condition, in which case duplicating this
issue and testing a fix may be problematic.
I've created a potential fix and tested this against our internal
regression tests, so it may be worth tying this to see if the issue
occurs with the fix.
To try this out do the follow
This bug has not been responded to from comment #1, so I'm marking this
bug as Won't Fix. If this is still and issue please re-open the bug and
we will re-visit this bug report.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because
** Summary changed:
- Problmes with disk size with zfs
+ Problems with disk size with zfs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897464
Title:
Problems with disk size with
So we have multiple levels of information here.
If you have 64GB of "drive space" I believe you are referring to the
partition size. If one allocates a whole pool to this then some of the
space is used as overhead to make the pool. This includes labelling,
alignment usage, metaslab allocation ove
@Tyson, hopefully the WBT changes helped to resolve this issue. If so,
please let me know and I can close this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1899249
Title:
Ope
OK, I'll close this bug for now. If it still bites please feel free to
re-open the bug and I'll get back onto it.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
ntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/19013
OK, Seems like we can resolve this by using some tuning. I was able to
reproduce this on a single drive SSD pool configuration with 30 clones
of the linux source and grep'ing for various strings.
So, the ARC determines that it can't free up enough memory by releasing
unpinned buffers so the prune
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are
Hi Hadmut,
>From your instructions it's not clean how you mounted these zfs file
systems. Can you prove the information on the commands you used so I can
try to reproduce this issue?
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Triaged
** Changed in: zfs-linux (Ubuntu)
Thanks Simon. Lets let this soak test for a few more weeks and then I'll
SRU this fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1900889
Title:
BUG: kernel NULL pointer derefere
Fix: commit 4230e2deaa484b385aa01d598b2aea8e7f2660a6 from
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
** Description changed:
- 5.8.0-1-generic (buildd@riscv64-qemu-lcy01-015) (gcc (Ubuntu
+ == SRU Groovy ==
+
+ Running the ftrace self tests results in null pointer dereference o
Excellent news.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814983
Title:
zfs poor sustained read performance from ssd pool
Status in Native ZFS for Linux:
Unknown
Status in z
Public bug reported:
Hit a build issue with:
commit 210acb0b35f61ce224fd08569ae2edb02123c3b4
Author: Casey Schaufler
Date: Fri Aug 21 14:29:19 2020 -0700
UBUNTU: SAUCE: Audit: Add new record for multiple process LSM
attributes
..in this section:
+{ }
+static inline int audit_log_task_c
Hi there,
can you provide details of how the upgrade was run and also which
releases were being upgraded from and to?
If possible a full history of installed packages may help me to figure
out why the upgrade failed by attaching /var/log/dkpg.log* to the bug
report and the currently installed pac
Public bug reported:
Add support for SiFive Unmatched
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/191
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894613
Title:
risc-v 5.8 kernel oops on ftrace tests
Status in u
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Also affects: linux (Ubuntu Groovy)
Importance:
are required for this
+ board support.
+
+ == The fix(es) ==
+
+ https://git.launchpad.net/~colin-king/+git/ubuntu-riscv-groovy
+
+ commits:
+ Christoph Hellwig (1):
+ riscv: move sifive_l2_cache.c to drivers/soc
+
+ Colin Ian King (1):
+ UBUNTU: [Config] Align configs with Unleashed
-01-11
+ 09:37:13 +)
+
+
Colin Ian King (1):
- UBUNTU: [Config] Align configs with Unleashed defconfigs
+ UBUNTU: [Config] Align configs with Unleashed defconfigs
- David Abdurachmanov (4):
- PCI: microsemi
https://twitter.com/asacasa/status/1287692205029765121
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1889080
Title:
ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-
Hi Alexander, in your tweet you mentioned it was "most likely a user
mistake though". Can we deduce that this is a genuine issue on upgrade
or was because of changes you made that caused this issue?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug not
(see https://twitter.com/asacasa/status/1287746641815113730 )
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1889080
Title:
ubuntu 18.04 dell OEM install broke after it auto upgraded to
: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1812620
Title:
msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
Status in ubu
Fix sent to mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-August/112505.html
https://lists.ubuntu.com/archives/kernel-team/2020-August/112506.html
** Description changed:
+ == SRU Justification [ FOCAL ] ==
+
+ The msg_zerocopy.sh kernel self test will fail on machines that d
Ran the tests with -proposed kernel on a 1 CPU system, tests now pass:
17:52:02 DEBUG| [stdout] # OK. All tests passed
17:52:02 DEBUG| [stdout] ok 21 selftests: net: msg_zerocopy.sh
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notif
: Undecided => High
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Chang
** Description changed:
== SRU Justification Focal, Groovy ==
Running the tcp_fastopen_backup_key.sh from net in
- ubuntu_kernel_selftests fails on little endian systems. This is a
+ ubuntu_kernel_selftests fails on big endian systems. This is a
regression that occurred because of commit
[ 139.952239] el0_sync+0x17c/0x180
[ 139.953894] Code: f101007f fa45a068 54fffc0b aa0303e2 (a9001d07)
[ 139.956946] ---[ end trace 71e2f9cc3eaddf4e ]---
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux
** Bug watch added: Linux Kernel Bug Tracker #208885
https://bugzilla.kernel.org/show_bug.cgi?id=208885
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=208885
Importance: Unknown
Status: Unknown
** Description changed:
+ Running:
+
+ sudo lcov --zerocounte
Ah, earlier on boot I'm seeing:
[8.808508] virtio_blk virtio3: [vda] 209715200 512-byte logical blocks (107
GB/100 GiB)
[8.808649] [ cut here ]
[8.815777] vda: detected capacity change from 0 to 107374182400
[8.816623] WARNING: CPU: 3 PID: 212 at mm/page_all
*** This bug is a duplicate of bug 1879470 ***
https://bugs.launchpad.net/bugs/1879470
** This bug has been marked a duplicate of bug 1879470
stress-ng on gcov enabled focal kernel triggers OOPS
--
You received this bug notification because you are a member of Kernel
Packages, which is su
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
@xnox,
one can detect the machine type from the DMI data (iff it is available
and reliable).
e.g. on my laptop:
sudo dmidecode -s "chassis-type"
Notebook
on my desktop server:
sudo dmidecode -s "chassis-type"
There are quite a few chassis-type, see
https://www.dmtf.org/sites/default/files/s
nvalid CPU addresses are not being sanity checked causing this issue.
The fix:
Upstream linux-next commit:
commit f49c7faf776f16607c948d852a03b04a88c3b583
Author: Colin Ian King
Date: Mon Aug 17 12:32:08 2020 +0100
of/address: check for invalid range.cpu_addr
** Affects: lin
Commit applied: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/groovy/commit/?h=master-
next&id=58c50e922166b40144af32c8d5049ab8ac93f483
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a membe
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-
Fix sent to mailing list for review: https://lists.ubuntu.com/archives
/kernel-team/2020-August/112820.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1885730
Title:
Please s
Tested for focal on arm64/amd64 generic and with PREEMPT with ubuntu zfs
tests - all OK.
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892001
Tested for bionic on arm64/am64 generic and amd64 with PREEMPT with
ubuntu zfs tests - all OK.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
Thanks Stefan, I gave this a test and it works as expected. Package
sponsored and uploaded.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902701
Title:
zfs-linux 0.8.3-1ubuntu12.4
** Also affects: zfs-linux (Ubuntu Hirsute)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Also affects: zfs-linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
I wonder if this is an issue with one of the dependency libraries that
got updated and now the bug does not occur. So far I can't reproduce
this issue either.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bug
Can you provide the output from dmesg so we can get an idea of what is
happening during boot?
** Changed in: linux-gcp (Ubuntu)
Status: New => Triaged
** Changed in: linux-gcp (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux-gcp (Ubuntu)
Importance: Undecided => High
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Bug watch added: Linux Kernel Bug Tracker #210175
https://bugzilla.kernel.org/show_bug.cgi?id=210175
** Also affects: linux via
https://bugzilla.kernel.org/sho
So I updated the firmware using the following capsule:
http://snapshots.linaro.org/components/kernel/leg-96boards-developerbox-
edk2/latest/DeveloperBox.Cap
sudo apt install fwupdate
wget
http://snapshots.linaro.org/components/kernel/leg-96boards-developerbox-edk2/latest/DeveloperBox.Cap
sudo fwu
I may be useful to add "debug ignore_loglevel" to the kernel boot
command line to get more debugging information during boot to see which
module is tripping this issue.
edit the /etc/default/grub (as the root user) and add the debug and
ignore_loglevel keywords to the GRUB_CMDLINE_LINUX_DEFAULT
G
** Summary changed:
- 5.10-rc1+ sdhci crash due to commit e0d072782c734d27f5af062c62266f2598f68542
+ 5.10-rc1+ sdhci crash due to commit
e0d072782c734d27f5af062c62266f2598f68542on Synquacer ARM64 dev box
--
You received this bug notification because you are a member of Kernel
Packages, which is
It maybe worth checking with one or more of the mainline kernels to see
if these behave differently from the Ubuntu kernel just to see if they
boot fine or if they suffer from the same issue.
The mainline kernels can be found in https://kernel.ubuntu.com/~kernel-
ppa/mainline
For example, it may
Thanks Ben, that's much appreciated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904054
Title:
kernel 5.8 general protection fault at boot
Status in linux package in Ubuntu:
Triag
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are
tested against 5.8 ftrace tests: NO crashing now, fixed.
cking@riscv64:~/linux/tools/testing/selftests/ftrace$ sudo ./ftracetest
=== Ftrace unit tests ===
[1] Basic trace file check [PASS]
[2] Basic test for tracers [PASS]
[3] Basic trace clock test [PASS]
[4] Basic event tracing c
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a
)
Status: New => Fix Committed
** Changed in: stress-ng (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: stress-ng (Ubuntu Groovy)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: In Progress => New
** Changed in: l
test not suitable for older S390x kernels at present, disabling it for
the moment.
Fix tested and committed:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=636eaaaf228f174ebf5701a920c99767fabc6da0
--
You received this bug notification because you are a member of Kern
Thanks for reporting back. I'll get this into the stable release updates
in a while.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1900889
Title:
BUG: kernel NULL pointer dereferenc
** Also affects: zfs-linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Hirsute)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Also affects: zfs-linux (Ubuntu Focal)
Importance: Undecided
** Also affects: zfs-linux (Ubuntu Hirsute)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: New
** Also affects: zfs-linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Groovy)
Importance: Undecided
Status
Upstream fix that has been backported is attached
** Patch added: "upstream patch"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+attachment/5438715/+files/0001-Bugfix-fix-uio-partial-copies.patch
--
You received this bug notification because you are a member of Kernel
Pac
I've uploaded the fixed package, it will be available in the -proposed
pocket for SRU testing at some point in the near future.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904589
T
Been digging into this a bit further with lxc 3.17 on Eoan.
lxc launch ubuntu:bionic zfs-bug-test
Creating zfs-bug-test
Starting zfs-bug-test
lxc delete zfs-bug-test --force
Error: Failed to destroy ZFS filesystem: Failed to run: zfs destroy -r
default/containers/z1: cannot destroy 'default/conta
** Changed in: thermald (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1811730
Title:
Thermald does not set max CPU after reseting th
This bug has been dormant for a while with no update. I'm marking it as
won't fix. If this is still and issue, please re-open this bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
IP addr Mac AddrKernel Reboots
13.64.67.18600:0d:3a:3a:dd:04 5.0.0-1016-azure50
104.42.152.115 00:0d:3a:35:b1:e6 5.0.0-1016-azure50
65.52.121.205 00:0d:3a:3b:0f:52 5.0.0-1016-azure50
13.88.28.42 00:0d:3a:3b:c7:da
See above, I ran several thousand reboot tests on a lot of Basic_A3
instances, ranging from 50, 250 to 500 reboots. Only one failed. So
this is *really* hard to reproduce.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ub
I kicked off another ~20K reboot tests with Standard_B2S instances and
hit hangs again:
IP addr Mac AddrKernel Reboots
104.42.3.16100:0d:3a:37:82:ee 5.0.0-1020-azure100
13.91.5.23 00:0d:3a:5a:74:23 5.0.0-1020-azure57 [
So the best way to reproduce this issue is to run ~500 reboots across
multiple instances rather than 5000-1 reboots on once instance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bug
See: https://github.com/lxc/lxd/issues/4656#issuecomment-535531229
In https://github.com/lxc/lxd/blob/master/lxd/storage_zfs_utils.go#L255
the umount is done by
err := unix.Unmount(mountpoint, unix.MNT_DETACH)
The umount2(2) manpage writes about MNT_DETACH:
Perform a lazy unmount: make
Get more failures with Standard_B1ms
IP addr Mac AddrKernel Reboots
52.160.101.11 00:0d:3a:5b:a0:7c 5.0.0-1020-azure10
137.135.51.101 00:0d:3a:31:20:fc 5.0.0-1020-azure500
137.135.50.133 00:0d:3a:31:27:0f 5.0.0-1020-azure396 [hang]
137.135.51.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-kernel-tests
Importance: Undecide
@Joseph, so I can reproduce this hang/crash issue across a variety of
instances. I can't get any info back on a console, so debugging this is
not easy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.lau
And for Standard_D2s_v3
IP addr Mac AddrKernel Reboots
104.42.252.54 00:0d:3a:32:df:92 5.0.0-1020-azure500
104.42.150.26 00:0d:3a:31:1b:50 5.0.0-1020-azure500
104.42.147.144 00:0d:3a:32:d8:2f 5.0.0-1020-azure500
40.112.129.232 00:0d:3a:32:d5
d in: ubuntu-kernel-tests
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Fix committed: https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=8e618fb7b00ecc206fe3ea73084492ebb5835747
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: ubuntu-kernel-tests
Status: Incomplete =&g
I've managed to reproduce this on pepe, seems like the autotest is being
OOM'd in preference to the actual cloning processes. I'll see if I can
figure out how to stop this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=7447c7b658e3a6cc40496a75033c007e4a91f166
** Changed in: stress-ng
Importance: Undecided => High
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: ubuntu-kernel
5.3 kernels then one can remove zfs-dkms.
Can you provide more information about the error?
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (
before calculating or verifying the
checksum in order to avoid spurious checksum failures.
https://bugzilla.kernel.org/show_bug.cgi?id=193661
Reported-by: Colin Ian King
Signed-off-by: Theodore Ts'o
Cc: sta...@vger.kernel.org
== Test case ==
Fire up an x86 VM with 8 or more CP
before calculating or verifying the
checksum in order to avoid spurious checksum failures.
https://bugzilla.kernel.org/show_bug.cgi?id=193661
Reported-by: Colin Ian King
Signed-off-by: Theodore Ts'o
Cc: sta...@vger.kernel.org
== Test case ==
Fire up an x86 VM with 8 or more
it
We must lock the xattr block before calculating or verifying the
checksum in order to avoid spurious checksum failures.
https://bugzilla.kernel.org/show_bug.cgi?id=193661
Reported-by: Colin Ian King
Signed-off-by: Theodore Ts'o
Cc: sta...@vger.kernel.org
== Test
This bug has been around since at least 2009.
Kernel Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195453
** Bug watch added: Linux Kernel Bug Tracker #195453
http://bugzilla.kernel.org/195453
** Also affects: linux via
http://bugzilla.kernel.org/195453
Importance: Unknown
This was fixed on the following version:
zfs-linux (0.6.5.9-5ubuntu1) zesty; urgency=medium
* Resynchronize with Debian, remianing changes:
- Load zfs module unconditionally for zesty
-- Aron Xu Mon, 20 Mar 2017 11:24:41 +0800
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed
** Changed in: zfs-linux (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624179
Title:
zfs property 'shareiscsi' listed in man page, but not
@Matthew, did Richard's advice help?
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628553
Title:
Ubuntu 16.04.1
** Summary changed:
- zfs not installed on yakety upgrade
+ zfs not installed on yakkety upgrade
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633557
Title:
zfs not installed on y
of all the packages installed on your system:
dpkg --get-selections > installed.log
and attached the installed.log to the bug report.
Thanks!
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (coli
thank you for reporting this. I've tried to reproduce this on an am64
Wily server upgrade to Xenial upgrade but I can't reproduce this. To
debug this further I require some extra information:
1. How did you perform the upgrade to Xenial?
2. Can you provide a list of all the packages installed on y
** Also affects: zfs via
https://github.com/zfsonlinux/zfs/issues/4999
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1615405
Title:
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1595286
Title:
package zfsutils-li
https://github.com/zfsonlinux/zfs/pull/4922
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packag
Can you attach the contents of the DKMS build log to the bug, I think it
should be named: /var/lib/dkms/zfs/0.6.5.9/build/make.log
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Status: Confir
901 - 1000 of 2264 matches
Mail list logo
