From: Joe Salmeri <jmscdba@gmail.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 6.6.1
Date: Sun, 5 Nov 2023 18:40:45 -0500 [thread overview]
Message-ID: <be0c51ba-86bd-44e7-884a-6cfccfa76184@gmail.com> (raw)
In-Reply-To: <aa605999-708c-4b8c-a05c-78fd2cc6b5b2@gmail.com>
Hi David,
Thanks for the info.
I'm using btrfsprogs 6.5.1-1.2 and my btrfs filesystem is a single
partition on a single device so it does not seem like the bugfix release
is related to my issue.
I actually think the issue occurred because of Skype crashing ( although
it does still seem a little odd to me that would cause the issue ).
Is there a way for btrfs to remove that directory entry which points to
the inode that does not exist ?
After I removed all the @home snapshots, that got rid of all of them
items that btrfs check reports EXCEPT for the one in the @home subvolume
so deleting a subvolume can remove the items, but I really don't want to
have to delete and restore the @home subvolume to fix it.
And since then btrfs has created new timeline snapshots for @home so
those obviously have the same issue as the ones I deleted but that
problem would go away if I can find a way to remove the offending item
in the @home subvolume.
Is there some way to remove that item ?
Running "ls -al /home/denise/.config/skypeforlinux/blob_storage/" also
shows that offending item:
drwx------ 1 denise joe-denise 72 Nov 1 22:49 .
drwxr-xr-x 1 denise joe-denise 3.7K Nov 1 20:07 ..
d????????? ? ? ? ? ?
02179466-b671-4313-8fa5-0eb87d716f92
I tried removing /home/denise/.config/skypeforlinux/blob_storage/ since
that is the folder that contains the
i02179466-b671-4313-8fa5-0eb87d716f92 directory item but that fails
rm -rf /home/denise/.config/skypeforlinux/blob_storage/
/usr/bin/rm: cannot remove
'/home/denise/.config/skypeforlinux/blob_storage/': Directory not empty
Joe
> On 11/5/23 17:20, David Sterba wrote:
>> Hi,
>>
>> btrfs-progs version 6.6.1 have been released. This is an important bugfix release,
>> v6.6 is broken and should not be used.
>>
>> Due to an accidental change in definition of the scanning ioctl in a
>> "documentation only" patch the mkfs or 'device scan' command were not able to
>> register all devices and mounting multi-device filesystems failed.
>> I misdiagnosed that as a change in the CI environment, thanks all early
>> packagers and testers for reports and the fix.
>>
>> Changelog:
>>
>> * fix device scanning ioctl definition, accidental change to the 'forget' ioctl
>> that breaks mounting multi-device filesystems
>>
>> Tarballs:https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
>> Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
>> Release:https://github.com/kdave/btrfs-progs/releases/tag/v6.6.1
> --
> Regards,
>
> Joe
--
Regards,
Joe
next prev parent reply other threads:[~2023-11-05 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 22:20 Btrfs progs release 6.6.1 David Sterba
[not found] ` <aa605999-708c-4b8c-a05c-78fd2cc6b5b2@gmail.com>
2023-11-05 23:40 ` Joe Salmeri [this message]
2023-11-09 14:38 ` David Sterba
2023-11-10 15:46 ` Joe Salmeri
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=be0c51ba-86bd-44e7-884a-6cfccfa76184@gmail.com \
--to=jmscdba@gmail.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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