From: Hanabishi Recca <irecca.kun@gmail.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, pali@kernel.org, dsterba@suse.cz,
aaptel@suse.com, willy@infradead.org, rdunlap@infradead.org,
joe@perches.com, mark@harmstone.com, nborisov@suse.com,
linux-ntfs-dev@lists.sourceforge.net, anton@tuxera.com,
dan.carpenter@oracle.com, hch@lst.de, ebiggers@kernel.org,
andy.lavr@gmail.com, kasep pisan <babam.yes@gmail.com>
Subject: Re: [PATCH v21 00/10] NTFS read-write driver GPL implementation by Paragon Software
Date: Sun, 14 Feb 2021 00:00:26 +0500 [thread overview]
Message-ID: <CAOehnrMK_9uP5j+QCF2qy_08yJEr_u9TEPwJJFogXQCeNFm6Gg@mail.gmail.com> (raw)
In-Reply-To: <20210212212737.d4fwocea3rbxbfle@spock.localdomain>
On Sat, Feb 13, 2021 at 2:27 AM Oleksandr Natalenko
<oleksandr@natalenko.name> wrote:
> Hanabishi, babam (both in Cc), here [2] you've reported some issues with
> accessing some files and with hidden attributes. You may reply to this
> email of mine with detailed description of your issues, and maybe
> developers will answer you.
There is strange files access issue since v18 update. Some random
files on partition became inaccessible, can't be read or even deleted.
For example:
# ls -la
ls: cannot access 'NlsStrings.js': No such file or directory
total 176
drwxrwxrwx 1 root root 4096 Oct 20 10:41 .
drwxrwxrwx 1 root root 12288 Oct 20 10:42 ..
-rwxrwxrwx 1 root root 8230 Oct 19 17:02 Layer.js < this file is ok
-????????? ? ? ? ? ? NlsStrings.js < this file is
inaccessible
...
To reproduce the issue try to mount a NTFS partition with deep
structure and large files amout. Then run on it some recursive file
command, e.g. 'du -sh', it will list all access errors.
Can't say what exactly causes it. Filesystem itself is not damaged,
when mounting it via ntfs-3g, ntfs3 <18 or in Windows it works
normally. The files is not damaged and chkdsk report no errors.
next prev parent reply other threads:[~2021-02-13 19:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:24 [PATCH v21 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 04/10] fs/ntfs3: Add file operations and implementation Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2021-02-12 18:12 ` Mark Harmstone
2021-02-12 16:24 ` [PATCH v21 06/10] fs/ntfs3: Add compression Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 07/10] fs/ntfs3: Add NTFS journal Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2021-02-12 16:24 ` [PATCH v21 10/10] fs/ntfs3: Add MAINTAINERS Konstantin Komarov
2021-02-24 7:52 ` Sebastian Gottschall
2021-02-12 21:27 ` [PATCH v21 00/10] NTFS read-write driver GPL implementation by Paragon Software Oleksandr Natalenko
2021-02-13 19:00 ` Hanabishi Recca [this message]
2021-02-15 7:07 ` kasep pisan
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=CAOehnrMK_9uP5j+QCF2qy_08yJEr_u9TEPwJJFogXQCeNFm6Gg@mail.gmail.com \
--to=irecca.kun@gmail.com \
--cc=aaptel@suse.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=andy.lavr@gmail.com \
--cc=anton@tuxera.com \
--cc=babam.yes@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=dsterba@suse.cz \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=joe@perches.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 \
/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).