From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
benjamin.haendel@gmx.net,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Tree-checker Issue / Corrupt FS after upgrade ?
Date: Mon, 17 Aug 2020 11:40:38 +0500 [thread overview]
Message-ID: <20200817114038.11b37d2f@natsu> (raw)
In-Reply-To: <CAJCQCtQo4yj=DSbH4JQZ0EiN5huXQwf1b7g0Bo826r53gSrWEg@mail.gmail.com>
On Sun, 16 Aug 2020 20:25:20 -0600
Chris Murphy <lists@colorremedies.com> wrote:
> On Fri, Aug 14, 2020 at 5:06 PM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> >
> > On 2020/8/15 上午3:05, benjamin.haendel@gmx.net wrote:
>
> > > 1. I am missing some folders and files
> > > 2. Some folders are there but no files in them
> > > 3. i can only access the drive via the samba share - not on the server directly
> > > 4. In Windows it shows "28TB of usage" but when i mark all data and hit alt+enter it counts to 21.1 TB only
> >
> > Windows? Why it's related to Windows then?
> > We're talking about btrfs, right?
> >
>
> Suggests the file system is being used with WinBtrfs.
>
> https://github.com/maharmstone/btrfs
Or just accessed via network from a Windows client, as hinted in point #3
about a Samba share.
But as for why behavior described in point #3 would be the case, no idea, that
sounds like something that's not really possible.
One possibility though is that a file manager that the user runs on the server
itself bails on showing a directory listing entirely, if it has some incorrect
entries in it (those that show up as ???????????? in 'ls'), but the Windows
one doesn't, or Samba doesn't export those in the first place. I'd suggest
examining the drive content from console with "ls" and not via any graphical
or even text-based file manager.
--
With respect,
Roman
prev parent reply other threads:[~2020-08-17 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 16:58 Tree-checker Issue / Corrupt FS after upgrade ? benjamin.haendel
2020-08-12 22:50 ` Qu Wenruo
[not found] ` <000801d670fd$bb2f62d0$318e2870$@gmx.net>
2020-08-12 23:29 ` AW: " Qu Wenruo
[not found] ` <003301d671a8$b93b8b60$2bb2a220$@gmx.net>
2020-08-14 0:46 ` AW: " Qu Wenruo
[not found] ` <000301d671b4$fc4a0650$f4de12f0$@gmx.net>
2020-08-14 0:56 ` Qu Wenruo
[not found] ` <003301d6726d$de5cbe30$9b163a90$@gmx.net>
2020-08-14 23:06 ` AW: " Qu Wenruo
2020-08-17 2:25 ` Chris Murphy
2020-08-17 6:40 ` Roman Mamedov [this message]
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=20200817114038.11b37d2f@natsu \
--to=rm@romanrm.net \
--cc=benjamin.haendel@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.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