From: Mohammad Rasim <mohammad.rasim96@gmail.com>
To: yanp.bugz@gmail.com
Cc: aaptel@suse.com, almaz.alexandrovich@paragon-software.com,
andy.lavr@gmail.com, anton@tuxera.com, dan.carpenter@oracle.com,
dsterba@suse.cz, ebiggers@kernel.org, hch@lst.de,
joe@perches.com, kari.argillander@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, mark@harmstone.com,
nborisov@suse.com, oleksandr@natalenko.name, pali@kernel.org,
rdunlap@infradead.org, viro@zeniv.linux.org.uk,
willy@infradead.org
Subject: Re: [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software
Date: Wed, 28 Jul 2021 19:23:34 +0300 [thread overview]
Message-ID: <2f310e28-49fe-3206-40d9-0c8a729f9227@gmail.com> (raw)
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
next reply other threads:[~2021-07-28 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:23 Mohammad Rasim [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 9:55 [PATCH v26 00/10] NTFS read-write driver GPL implementation by Paragon Software Marius Cirsta
2021-04-02 15:53 Konstantin Komarov
2021-05-19 3:47 ` Neal Gompa
2021-05-19 3:51 ` Neal Gompa
2021-05-20 16:13 ` Darrick J. Wong
2021-07-17 16:36 ` Pali Rohár
2021-07-25 17:02 ` Yan Pas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f310e28-49fe-3206-40d9-0c8a729f9227@gmail.com \
--to=mohammad.rasim96@gmail.com \
--cc=aaptel@suse.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=andy.lavr@gmail.com \
--cc=anton@tuxera.com \
--cc=cc64ac69-f4e5-3fc4-1362-ced7cf68119a@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=dsterba@suse.cz \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=kari.argillander@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=mark@harmstone.com \
--cc=nborisov@suse.com \
--cc=oleksandr@natalenko.name \
--cc=pali@kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yanp.bugz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).