fsync: giving up on dirty

[Artem Kuchin]

Just upgraded from 10.1 to 10.2 via sources.

After reboot received this:

Jan  1 16:37:41 omni kernel: fsync: giving up on dirty
Jan  1 16:37:41 omni kernel: 0xfffff8000f22cb10: tag devfs, type VCHR
Jan  1 16:37:41 omni kernel: usecount 1, writecount 0, refcount 77 
mountedhere 0xfffff8000f0b2e00
Jan  1 16:37:41 omni kernel: flags (VI_ACTIVE)
Jan  1 16:37:41 omni kernel: v_object 0xfffff8000f244200 ref 0 pages 587 
cleanbuf 74 dirtybuf 1
Jan  1 16:37:41 omni kernel: lock type devfs: EXCL by thread 
0xfffff8000cfae4a0 (pid 22, syncer, tid 100089)
Jan  1 16:37:41 omni kernel: dev mirror/root

Tried to work. Got more same messages.

/ is gmirror

# gmirror status
        Name    Status  Components
mirror/boot  COMPLETE  ada0p1 (ACTIVE)
                        ada1p1 (ACTIVE)
mirror/swap  COMPLETE  ada0p2 (ACTIVE)
                        ada1p2 (ACTIVE)
mirror/root  COMPLETE  ada0p3 (ACTIVE)
                        ada1p3 (ACTIVE)


# tunefs -p /
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       enabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  4096
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             8%
tunefs: space to hold for metadata blocks: (-k)            6408
tunefs: optimization preference: (-o)                      time
tunefs: volume label: (-L)                                 root

now disabled soft updates journaling and error went away.

Maybe need to disable and reenable SU journaling? I google and see such 
error dates back to 2012. Apparently it still
happens. Why?


Artem