Bug 180876 - [zfs] [hast] ZFS with trim,bio_flush or bio_delete locks hast device write operations
Summary: [zfs] [hast] ZFS with trim,bio_flush or bio_delete locks hast device write op...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-26 12:50 UTC by ivk
Modified: 2017-12-31 22:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ivk 2013-07-26 12:50:00 UTC
I've run hast synchronization from primary to secondary. Within some time of synchronization run zpool status zroot. zpool shows status of zroot and after some seconds hast syncronization stops. In that some seconds only 6-10Mb writes to primary device. I've see that in dirty section from "hastctl list". Any write operations to zfs pool stops too. I can't mount zfs filesystem datasets anymore. Only ACPI button poweroff or Ctrl+Alt+Delete works with some small timeouts.

Fix: 

vfs.zfs.vdev.bio_delete_disable=1
vfs.zfs.vdev.bio_flush_disable=1

fix my problem. May be only one of them or vfs.zfs.trim.enabled=0. Didn't check, sorry.
How-To-Repeat: - create hast device on primary
- create ZFS pool on primary hast device
- create hast device on secondary
- run synchronization (memory type) from primary to secondary
- make some write operations on primary ZFS pool: create datasets, mount datasets, write some files.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-07-26 22:44:29 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Mikolaj Golub freebsd_committer freebsd_triage 2013-07-28 19:25:19 UTC
I have failed to reproduce the issue. So could you give more details?

It would be nice to see your configs and logs from both primary and
secondary, and the sequence of commands that led to the hang.

Also, it would be very nice to find out exactly what option (or
combination) caused the issue.

-- 
Mikolaj Golub
Comment 3 ivk 2013-07-29 03:36:49 UTC
This is a multi-part message in MIME format.
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:37 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped