[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2f310e28-49fe-3206-40d9-0c8a729f9227@gmail.com>
Date: Wed, 28 Jul 2021 19:23:34 +0300
From: Mohammad Rasim <mohammad.rasim96@...il.com>
To: yanp.bugz@...il.com
Cc: aaptel@...e.com, almaz.alexandrovich@...agon-software.com,
andy.lavr@...il.com, anton@...era.com, dan.carpenter@...cle.com,
dsterba@...e.cz, ebiggers@...nel.org, hch@....de, joe@...ches.com,
kari.argillander@...il.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-ntfs-dev@...ts.sourceforge.net,
mark@...mstone.com, nborisov@...e.com, oleksandr@...alenko.name,
pali@...nel.org, rdunlap@...radead.org, viro@...iv.linux.org.uk,
willy@...radead.org
Subject: Re: [PATCH v26 00/10] NTFS read-write driver GPL implementation by
Paragon Software
Hi,
I've been using your ntfs driver for sometime now and it's great to
finally have a good driver for this FS, however i have problem where if
the power cuts off from my system while writing to the volume the
partition gets corrupted, this is expected of course but the problem is
that `ntfsfix` tool can't fix the partition and no matter how many times
i run it the system will always spits this in the kernel log when trying
to mount the partition:
ntfs3: sdb1: volume is dirty and "force" flag is not set!
if i boot to a windows 10 OS then the system is able to mount the volume
with no problem(even before running chkdsk on it), windows `chkdsk`
utility can find the errors and fix them, and i can reboot to linux to
use my partition again with no problem.
it would be nice to have your filesystem utilites published on github so
we can use them with the current out of the tree driver
Regards
Powered by blists - more mailing lists