I've not heard back on any feedback for information from comment #1, so
I'm going to mark this as "Won't Fix". If this is still and issue,
please re-open the bug and provide debugging feedback as requested.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received
I'm going to mark this as "Won't Fix" as this issue is not occurring
with the zil_slog_limit change and I've not fixed anything. If this
problem re-occurs please re-open this bug.
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification
This stack trace is similar to one in
https://github.com/zfsonlinux/zfs/issues/2934 - the suspected issue is
that one of the devices is taking a long time to complete and ZFS is
blocked waiting for this.
I suggest installing sysstat
sudo apt install sysstat
and when the lockup happens run:
Vasiliy, please refer to comment #8
--
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/1781364
Title:
Kernel error "task zfs:pid blocked for more than 120 seconds"
Status in Linux:
The kernel driver fix will land in the next -proposed kernel as the
Ubuntu ZFS driver comes bundled with the kernel.
If you build zfs from source, then that will build the kernel driver as
a DKMS module with the fix in it and *that* will work.
One needs both the zfs userspace and the kernel for
This fix will only work once it lands in the updated kernel as well as
the user space packages, so please test once the updated kernel is also
in -proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
*** This bug is a duplicate of bug 1781364 ***
https://bugs.launchpad.net/bugs/1781364
** This bug has been marked a duplicate of bug 1781364
Kernel error "task zfs:pid blocked for more than 120 seconds"
--
You received this bug notification because you are a member of Kernel
Packages,
@Rafael, did the workaround in comment #31 help?
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => 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/1654517
** Description changed:
- == SRU Justification, BIONIC ==
+ == SRU Justification, XENIAL, BIONIC ==
Exercising ZFS with lxd with many mount/umounts can cause lockups and
120 second timeout messages.
== How to reproduce bug ==
In a VM, 2 CPUs, 16GB of memory running Bionic:
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
** Description changed:
+ == SRU Justification, BIONIC ==
+
+ Exercising ZFS with lxd with many mount/umounts can cause lockups and
+ 120 second timeout messages.
+
+ == How to reproduce bug ==
+
+ In a VM, 2 CPUs, 16GB of memory running Bionic:
+
+ sudo apt update
+ sudo apt install lxd
** Tags removed: verification-done-bionic
** Tags added: verification-needed-xenial
--
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/1759848
Title:
Allow multiple mounts of zfs
Tested with kernel 4.15.0-27-generic and the fix works. Marking as
verified for Bionic.
** 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/1759848
)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Also affects: zfs-linux (Ubuntu Cosmic)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
proc_inode_cache
248320 233052 0%0.01K485 512 1940K kmalloc-8
214984 143177 0%0.57K 3839 56122848K radix_tree_node
** Affects: linux
Importance: Unknown
Status: Unknown
** Affects: linux (Ubuntu)
Importance: Hig
I would be useful to see if a non-SMP boot will cause the same issue; if
it only occurs in SMP boots then we know it's a lower level locking/race
style of problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It may be worth grabbing a copy of the /proc/sys on a clean boot and
then a copy after the sysctl changes so we can get and idea of any
specific tweaks that may have occurred.
Just to note, I've been running the stress-ng command as noted in
comment #3 on a 24 CPU ARM64 Synquacer box with the
What is the stress-ng command that is being run by /usr/lib/plainbox-
provider-checkbox/bin/disk_stress_ng - without knowing that it's hard to
figure out the initial stressor conditions
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- failure to boot with inux-image-4.15.0-24-generic
+ failure to boot with linux-image-4.15.0-24-generic
--
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/1779827
Title:
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Won't Fix
** Summary changed:
- zfs utils and kernel version mismath
+ zfs utils and kernel version mismatch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
do find interoperability issues please file a
separate bug for any issues you find.
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Impo
ZFS is not supported on 32 bit platforms because of the need for large
amounts of memory for various ZFS caches. If you require ZFS, please use
a 64 bit kernel. Marking as Won't fix.
** Changed in: zfs-linux (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because
We need to wait until the kernel is updated with the fix before it can
be tested as the fixes require kernel + zfs together to work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
This SRU requires and update in zfsutils-linux and the change sync'd to
the kernel and the kernel update to complete the 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/1759848
** Description changed:
- Pull upstream fix https://trello.com/c/l89Ygj28/352-allow-multiple-
- mounts-of-zfs-datasets to allow multiple mounts
+ === SRU Justification, Xenial ==
An attempt to mount an already mounted zfs dataset should return a new
mount referencing the existing super
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Colin Ian King (colin-king)
** No longer affects: linux (Ubuntu Artful)
** No longer affects: zfs-linux (Ubuntu Artful)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Xenial)
OK, I'll mark that as fixed-released.
** 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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1725339
Title:
ZFS
** Changed in: linux (Ubuntu Cosmic)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
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/1772024
Title:
linux 4.13.0-42.47 ADT t
Tested with 0.6.5.6-0ubuntu23 inside a xenial lxc container and the 10
second delay is now fixed.
** Tags added: ve
** Changed in: zfs-linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu Artful)
Importance: Undecided => High
** Changed in: zfs-linux
Tested with 0.6.5.11-1ubuntu3.6 inside an artful lxc container and the
10 second delay is now fixed.
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Tested with 0.7.5-1ubuntu16.2 inside a bionic lxc container and the 10
second delay is now fixed.
** 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.
** Changed in: zfs-linux (Ubuntu Bionic)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu Xenial)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu Artful)
Assignee: (unassigned) => Colin Ian Ki
..plus it can be easily checked w/o any special privilege.
--
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/1760173
Title:
zfs, zpool commands hangs for 10 seconds without a /dev/zfs
So, I am pretty confident that systemd will create
"/run/systemd/container" if we're inside a container, so I'll check for
that
--
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/1760173
OK, I hadn't realized that, so much for my trivial testing. So, is
there any simple way for any process inside a container to detect if one
is inside a containerized environment without any special root
privileges?
--
You received this bug notification because you are a member of Kernel
I'm confused too then, how is that when I start a process inside the
container, such as from a shell it can access this environment variable
and my fix works?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Description changed:
+ == SRU Justification, Xenial, Artful, Bionic ==
+
+ When outside a lxd container with zfs storage, zfs list or zpool status
+ either returns or reports what's going on.
+
+ When inside a lxd container with zfs storage, zfs list or zpool status
+ appears to hang, no
)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: Triaged
** Also affects: lxd (Ubuntu Cosmic)
Importance: Undecided
Status: Invalid
** Also affects: zfs-linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lxd (Ubuntu Bionic
signed) => Colin Ian King (colin-king)
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => Critical
--
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/1774571
Title:
sigq test fr
That makes sense. We need to force remove that module then.
--
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/1751213
Title:
kernel security test report that the lttng_probe_writeback
Test kernel packages have been uploaded ready for testing:
http://kernel.ubuntu.com/~cking/lp1772617/
Please test these and report if this fixes the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
Yo
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => Invalid
--
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/1766308
Title:
inexplicably large file reported by zfs filesystem
** Description changed:
== SRU Justification ==
IBM reports a kernel crash with Bionic while in degraded mode(Degraded
cores).
IBM created a patch to resolve this bug and has submitted it upstream:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-May/172835.html
- The patch
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
ged
** 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 a member of Kernel
Packages, which is subscribed to zfs-linux in Ubun
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1768777
Title:
libnvpair1linux doc contents have busted
Installed a Xenial server and then zfsutils-linux. Upgraded to Bionic
with -proposed enabled and the symlinks are not broken with zfsutils-
linux 0.7.5-1ubuntu16 - marking as verified
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of
** Description changed:
+ == SRU Justification ==
+
+ Upgrading from Xenial to Bionic causes broken symlinked changelog,
+ COPYRIGHT and OPENSOLARIS.LICENSE.gz files because the zfs-doc file is
+ missing.
+
+ == Fix ==
+
+ Add back the missing zfs-doc package, with this package the upgrade
+
This seems to only occur with a Xenial -> Artful or Xenial -> Bionic
upgrades and not Artful -> 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/1768777
Title:
libnvpair1linux
I meant to say "just close this bug against 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/1766308
Title:
inexplicably large file reported by zfs filesystem
Status in
Thanks Matt for the update. Shall we just this bug against ZFS then?
--
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/1766308
Title:
inexplicably large file reported by zfs filesystem
Couple of notes:
1. This is not an issue with clean install of zfsutils-linux
2. Removing zfsutils-linux and an autoremove with a re-install fixes this
3. This occurs on an upgrade from a previous release if I understand the issue
correctly.
** Changed in: zfs-linux (Ubuntu)
Importance:
This is fix to a regression from a previous SRU, I don't have the H/W at
hand to test this, so I can't verify it.
--
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/1764810
Title:
Xenial:
** 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/1768777
Title:
libnvpair1linux
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
And if anyone is wondering why this is not the default, the answer is
here: https://github.com/zfsonlinux/zfs/issues/443
** Bug watch added: Github Issue Tracker for ZFS #443
https://github.com/zfsonlinux/zfs/issues/443
--
You received this bug notification because you are a member of Kernel
You can get an idea of how "full" a file is using zdb, e.g:
sudo zdb -O pool-ssd/virt ubuntu17.10-amd64-desktop.qcow2
Object lvl iblk dblk dsize dnsize lsize %full type
1147373 128K 128K 14.0G 512 20.0G 84.49 ZFS plain file
in the above example,
Ah, that is a good solution. By default, ZFS on Linux will store xattrs
in a hidden folder, so there are multiple seeks per xattr and it's
poorly cached, so it will impact on performance especially on the slower
block devices. The zfs set xattr=sa will store this in the inodes and
will really
I've tried to simulate this with very slow media and can't yet reproduce
this issue. Can you play the DVD image and also run the following
command in another terminal:
iostat 1 300 > iostat.log
this will capture 5 minutes of activity. please then attach the log to
the bug report.
--
You
@Matt, did the above help?
--
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/1766308
Title:
inexplicably large file reported by zfs filesystem
Status in zfs-linux package in Ubuntu:
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Changed in: zfs-linux (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => 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/1766964
Title:
zpool status -v aborts with SIGABRT with and
Hrm. I'm, included to have the container environment inform zfs that
the timeout should be zero rather adding in more logic to zfs that tries
to determine which environment it is in to determine the timeout time.
The container environment just needs to set the 1 environment variable
that ZFS
=> Triaged
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => 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/1724165
Title:
receive_freeobjects() skips freeing some
ed 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/1766964
Title:
zpool status -v aborts with SIGAB
The code actually polls /dev/zfs until it appears. The issue here is
that it does not appear after 10 seconds, and then it gives up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
accessing /dev/zfs is dependent on loading the zfs module which may take
some time for udev to do it's work to create /dev/zfs. However, ZFS
does allow this to be tweaked with the ZFS_MODULE_TIMEOUT environment
variable:
>From lib/libzfs/libzfs_util.c, libzfs_load_module:
/*
* Device creation
*** This bug is a duplicate of bug 1742698 ***
https://bugs.launchpad.net/bugs/1742698
** This bug has been marked a duplicate of bug 1742698
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
--
You received this bug notification because you are a member of Kernel
Packages,
OK, lets keep this bug open for a few more months and if you see the
problem again, please update the bug report.
--
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/1722261
Title:
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
** Changed in: zfs-linux (Ubuntu)
Status: I
After debugging the object code, I can see that the error occurs because
of corruption in the internal AVL tree; the bug occurs during an
insertion into the AVL tree in avl_insert(), namely when nullifying
node->avl_child[0]:
node->avl_child[0] = NULL;
node->avl_child[1] = NULL;
** No longer affects: 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/1749715
Title:
general protection fault in zfs module
Status in zfs-linux package in Ubuntu:
Confirmed
Without more specific information I'm unable to reproduce this issue.
I'm going to mark it as Won't Fix.
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
@Aleberto, any feedback from comment #5 would be appreciated.
--
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/1722261
Title:
deadlock in mount umount and sync
Status in zfs-linux
@Simon, the log in comment #8 contains different crashes so I'm going to
focus on the original crash report on comment #1. Has this problem re-
occurred with more recent kernels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
Just one more check, what is the block size of the raw devices? One can
check this using:
sudo blockdev --getpbsz /dev/sdb
sudo blockdev --getpbsz /dev/sdc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Tested on Artful with 4.15.0-20, works fine now with this fix too.
** Description changed:
== SRU Justification [XENIAL][ARTFUL] ==
Symlinks in /dev/zvol are not because /lib/udev/zvol_id exits with
ioctl_get_msg failed:Inappropriate ioctl for device. The core reason is
that the
Note: this does not need fixing for Bionic as the ZFS 0.7.x userspace
tools work fine with the 4.15 bionic kernel.
** Changed in: zfs-linux (Ubuntu Xenial)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu Artful)
Assignee: (unassigned) => Col
Tested on Xenial with HWE kernel 4.15.0-15 (#16~16.04.1), works fine
with this fix.
** Description changed:
== SRU Justification [XENIAL][ARTFUL] ==
Symlinks in /dev/zvol are not because /lib/udev/zvol_id exits with
ioctl_get_msg failed:Inappropriate ioctl for device. The core reason
Just to note, this is a compat fix for older versions of the user space
tools to work with newer ZFS 0.7.x, so the fix is not required in
Bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Description changed:
- == SRU Justifcation [XENIAL][ARTFUL] ==
+ == SRU Justification [XENIAL][ARTFUL] ==
Symlinks in /dev/zvol are not because /lib/udev/zvol_id exits with
ioctl_get_msg failed:Inappropriate ioctl for device. The core reason is
that the BLKZNAME with non-HWE
** Description changed:
+ == SRU Justifcation [XENIAL][ARTFUL] ==
+
+ Symlinks in /dev/zvol are not because /lib/udev/zvol_id exits with
+ ioctl_get_msg failed:Inappropriate ioctl for device. The core reason is
+ that the BLKZNAME with non-HWE userspace zfsutils is 1 char different is
+ size
I'm tracking the fix in Ubuntu with bug report 1765572
--
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/1764320
Title:
Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Thanks Ben for spotting the bug and for the fix, I'm uploading that to
Debian right now and will sync it into Ubuntu as soon as it is ready for
syncing. Much appreciated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Not sure why there is little activity on the upstream bug report.
If you are using ZFS intent log, it may be worth trying to set it to a
fairly large size, such as 128 or 256MB using the zil_slog_limit
setting.
--
You received this bug notification because you are a member of Kernel
Packages,
I'm adding a small change to thermald so it does not continually spam
the log.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: thermald (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of
** Description changed:
+ == SRU Justification ==
+
A previous backport to bug LP: #1745130 overlooked adding in
an error return that was introduced by commit 6124c53edeea. Fix
this by adding in the missing return.
Detected by CoverityScan, CID#1467925 ("Missing return statement)
Couple of things:
1. Next time this occurs, can you run the following command and paste
the output into the bug report:
sudo zpool events -v
That may provide some additional information on what state the IOs are
in.
2. If you are using ZFS intent log, it may be worth trying to set it to
a
** Description changed:
== SRU Justification, ARTFUL ==
Bug fix #1747069 causes an issue for NVIDIA drivers on ppc64el
platforms. According to Will Davis at NVIDIA:
"- The original patch 3d79a728f9b2e6ddcce4e02c91c4de1076548a4c changed
the call to arch_add_memory in
Thanks for verifying Joshua. Much appreciated!
--
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/1754584
Title:
zfs system process hung on container stop/delete
Status in Native ZFS
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: New => In
** Description changed:
SRU Justification, bionic
Apply the first round of SRU bugfixes for ZFS from 0.7.5 onwards from
upstream ZFS repository. This round fixes the following ZFS bugs:
- - OpenZFS 8373 - TXG_WAIT in ZIL commit path
- Closes zfsonlinux #6403
- - zfs
re core functionality
works and there is minimized risk of lost of data and core functionality
== Testing ==
Run ubuntu ZFS ADT regression tests in autotest-client-tests git repository.
With the fixes, none of this should fail, hang or regress.
** Affects: zfs-linux (Ubuntu)
Impo
The logs would be useful, maybe I can figure out something from them.
Thanks!
--
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/1749715
Title:
general protection fault in zfs module
The iostat -mx shows that the /dev/sdb /dev/sdc devices have a very high
read I/O latency of ~80-110 milliseconds which may be the underlying
issue.
I suggest seeing how long it takes to read data from these raw devices
to sanity check their maximum speed. One can do this by doing:
sync
echo 3
** Changed in: zfs-linux (Ubuntu)
Importance: Medium => High
--
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/1760173
Title:
zfs, zpool commands hangs for 10 seconds without a
1201 - 1300 of 2248 matches
Mail list logo
