9.5

Table Of Contents

User manual 14

dmesg | tail or so

In that case more information can be obtained using the following command:

# dmesg | tail | grep ufsd

[ 369.844741] ufsd: volume is dirty and "force" flag is not set

Lines related to UFSD driver start with ’ufsd:’ preﬁx. In case Kernel log is redirected to console,

messages may be output to terminal window right after mount command is issued:

# mount -t ufsd /dev/sdd1 /mnt/sdd1

ufsd: volume is dirty and "force" flag is not set

mount: wrong fs type, bad option, bad superblock on /dev/sdd1,

missing codepage or helper program, or other error

In some cases useful info is found in syslog - try

dmesg | tail or so

In this example dmesg output contains information that the volume being mounted is ‘dirty’. See Dirty

ﬂag issues subsection for more information on ‘dirty’ ﬂag and how to resolve the issue.

Dismount volumes

To dismount volumes mounted by UFSD driver issue usual umount command:

# umount /dev/sdd1

See Why the disk can’t be dismounted? subsection for more information, if the volume can’t be

dismounted.

4.3 Dirty ﬂag issues

‘Dirty’ ﬂag is special feature implemented in most of the modern ﬁle systems, including NTFS and

HFS+. This ﬂag is set after volume is mounted in read/write mode and cleared after volume is correctly

unmounted (see notes on ’force’ mount option for more information). Without ‘dirty’ ﬂag it is impossible

to tell if given volume was correctly unmounted or not. Detecting incorrectly unmounted volumes helps

to detect possible errors as early as possible. Thus, this ﬂag helps to preserve ﬁle system consistency.

Please note that even in case ‘dirty’ ﬂag is set on the volume, ﬁle system is not necessarily corrupt.

Paragon NTFS&HFS+ for Linux drivers from version 8 support ‘dirty’ ﬂag on both NTFS and HFS+.

By default, driver refuses to mount volumes with ‘dirty’ ﬂag set. Recommended course of action is to

check the volume for errors and repair any inconsistencies found using chkntfs/chkhfs utility with

-a -f command line options (see Additional Utilities). Run with -a command line option, the utilities

check dirty ﬂag state and in case it is set, they performs all necessary checks. If ‘dirty’ ﬂag is not

set, ﬁle system checking utilities exits immediately. If -f command line option is speciﬁed, the utilities

repair any errors or inconsistencies that they ﬁnd and ﬁnally clear ‘dirty’ ﬂag. This approach is similar

to the way Windows and MacOS handle ‘dirty’ volumes. See corresponding sections on NTFS and

HFS+ utilities and ‘File system checking utilities return codes’ section for more information.

To make driver mount dirty volumes without checking for possible errors and correcting them, ’force’

mount option can be used (while it is not recommended). This way, ‘dirty’ ﬂag is not cleared and any

possibly existing errors or inconsistencies are not ﬁxed. ‘Dirty’ ﬂag will remain set until volume is

checked for errors using Paragon chkntfs/chkhfs with -f command line option or using Windows

chkdsk utility with /f switch or MacOS Disk Utility (for NTFS and HFS+ volumes, respectively).

Paragon Technologie GmbH

Leo-Wohleb-Straße 8, 79098 Freiburg, Germany