On 2021/03/29 12:34, Anand Jain wrote:
> On 15/03/2021 13:53, Naohiro Aota wrote:
>> The following patch will change the superblock logging zones' location from
>> fixed zone number to fixed LBAs.
>>
>> Here is a background of how the superblock is working on zoned btrfs.
>>
>> This document will b
> Gesendet: Montag, 29. März 2021 um 01:02 Uhr
> Von: "Chris Murphy"
> An: "B A"
> Cc: "Btrfs BTRFS"
> Betreff: Re: Help needed with filesystem errors: parent transid verify failed
>
> On Sun, Mar 28, 2021 at 9:41 AM B A wrote:
> >
> > Dear btrfs experts,
> >
> >
> > On my desktop PC, I have 1
> Gesendet: Montag, 29. März 2021 um 01:02 Uhr
> Von: "Chris Murphy"
> An: "B A"
> Cc: "Btrfs BTRFS"
> Betreff: Re: Help needed with filesystem errors: parent transid verify failed
>
> On Sun, Mar 28, 2021 at 9:41 AM B A wrote:
> >
> > Dear btrfs experts,
> >
> >
> > On my desktop PC, I have 1
Looks good,
Reviewed-by: Johannes Thumshirn
On Mon, Mar 29, 2021 at 1:34 AM B A wrote:
>
> This is a very old BTRFS filesystem created with Fedora *23* i.e. a linux
> kernel and btrfs-progs around version 4.2. It was probably created 2015-10-31
> with Fedora 23 beta and kernel 4.2.4 or 4.2.5.
>
> I ran `btrfs scrub` about a month ago with
> Gesendet: Montag, 29. März 2021 um 08:09 Uhr
> Von: "Chris Murphy"
> An: "B A" , "Btrfs BTRFS"
> Cc: "Qu Wenruo" , "Josef Bacik"
> Betreff: Re: Re: Help needed with filesystem errors: parent transid verify
> failed
> […]
>
> What do you get for:
>
> btrfs insp dump-s -f /dev/dm-0
See attac
On Thu, Mar 18, 2021 at 10:42 AM Ondrej Mosnacek wrote:
> On Tue, Mar 16, 2021 at 8:25 PM Al Viro wrote:
> > On Tue, Mar 16, 2021 at 02:21:45PM -0400, Paul Moore wrote:
> > > On Tue, Mar 16, 2021 at 10:48 AM Ondrej Mosnacek
> > > wrote:
> > > >
> > > > When SELinux security options are passed t
Hello,
I have a filesystem which is sometimes very slow, or even currently
hangs deleting a file (plain and simple rm in bash).
Label: 'DataPool1' uuid: c4a6a2c9-5cf0-49b8-812a-0784953f9ba3
Total devices 2 FS bytes used 5.65TiB
devid1 size 7.28TiB used 6.71TiB path /dev/sd
I'm Evelyn, I need to discuss something with you, I hope we can start a
relationship from here. I hope to come here soon. Thanks.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Dear list,
due to a disk intermittently failing in my 4 disk array, I'm getting "transid
verify failed" errors on my btrfs filesystem (see attached dmesg | grep -i
btrfs dump in btrfs_dmesg.txt). When I run a scrub, the bad disk (/dev/sdd)
becomes unresponsive, so I'm hesitant to try that
again
Hi,
I am currently investigating the possibility to use `btrfs-stream` files
(generated by `btrfs send`) for deploying a image based update to
systems (probably embedded ones).
One of the issues I encountered here is that btrfs-send does not use any
diff algorithm on files that have changed
On 3/29/21 4:42 AM, B A wrote:
Gesendet: Montag, 29. März 2021 um 08:09 Uhr
Von: "Chris Murphy"
An: "B A" , "Btrfs BTRFS"
Cc: "Qu Wenruo" , "Josef Bacik"
Betreff: Re: Re: Help needed with filesystem errors: parent transid verify
failed
[…]
What do you get for:
btrfs insp dump-s -f /dev/dm-0
On 29.03.2021 16:16, Claudius Heine wrote:
> Hi,
>
> I am currently investigating the possibility to use `btrfs-stream` files
> (generated by `btrfs send`) for deploying a image based update to
> systems (probably embedded ones).
>
> One of the issues I encountered here is that btrfs-send does no
Am Mon, 29 Mar 2021 19:30:34 +0300
schrieb Andrei Borzenkov :
> On 29.03.2021 16:16, Claudius Heine wrote:
> > Hi,
> >
> > I am currently investigating the possibility to use `btrfs-stream`
> > files (generated by `btrfs send`) for deploying a image based
> > update to systems (probably embedded
On 29.03.2021 19:25 Henning Schild wrote:
> Am Mon, 29 Mar 2021 19:30:34 +0300
> schrieb Andrei Borzenkov :
>
>> On 29.03.2021 16:16, Claudius Heine wrote:
>>> Hi,
>>>
>>> I am currently investigating the possibility to use `btrfs-stream`
>>> files (generated by `btrfs send`) for deploying a image
On Mon, Mar 29, 2021 at 5:12 AM Hendrik Friedel wrote:
>
> Hello,
>
> I have a filesystem which is sometimes very slow, or even currently
> hangs deleting a file (plain and simple rm in bash).
>
> Label: 'DataPool1' uuid: c4a6a2c9-5cf0-49b8-812a-0784953f9ba3
> Total devices 2 FS bytes us
On Fri, Mar 26, 2021 at 01:14:41PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> There is a comment at btrfs_replace_file_extents() that mentions that we
> set the full sync flag on an inode when cloning into a file with a size
> greater than or equals to 16MiB, through try_release_
On Thu, Mar 25, 2021 at 10:41:43PM +0800, Anand Jain wrote:
> On 25/03/2021 15:14, Qu Wenruo wrote:
> > +static ssize_t supported_sectorsizes_show(struct kobject *kobj,
> > + struct kobj_attribute *a,
> > + char *buf)
> > +{
>
On Wed, Mar 24, 2021 at 09:44:21AM -0400, Josef Bacik wrote:
> Looking at perf data for a fio workload I noticed that we were spending
> a pretty large chunk of time (around 5%) doing percpu_counter_sum() in
> need_preemptive_reclaim. This is silly, as we only want to know if we
> have more ordere
On Wed, Mar 24, 2021 at 11:23:11PM +0900, Naohiro Aota wrote:
> Commit 6e37d2459941 ("btrfs: zoned: fix deadlock on log sync") pointed out
> a deadlock warning and removed
> mutex_{lock,unlock}(&fs_info->tree_root->log_mutex). While it looks like it
> always cause a deadlock, we didn't see actual d
On Thu, Mar 25, 2021 at 09:56:22AM +0800, bingjingc wrote:
> From: BingJing Chang
>
> In commit d77815461f04 ("btrfs: Avoid trucating page or punching hole
> in a already existed hole."), existed holes can be skipped by calling
> find_first_non_hole() to adjust *start and *len. However, if the gi
On Tue, Mar 23, 2021 at 03:31:19PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> gcc complains that the ctl->max_chunk_size member might be used
> uninitialized when none of the three conditions for initializing it in
> init_alloc_chunk_ctl_policy_zoned() are true:
>
> In function ‘init_
On Tue, Mar 23, 2021 at 06:39:49PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> If we reflink to or from a file opened with O_SYNC/O_DSYNC or to/from a
> file that has the S_SYNC attribute set, we totally ignore that and do not
> durably persist the reflink changes. Since a reflink
On Thu, Mar 25, 2021 at 03:14:32PM +0800, Qu Wenruo wrote:
> v3:
> - Rename the sysfs to supported_sectorsizes
>
> - Rebased to latest misc-next branch
> This removes 2 cleanup patches.
>
> - Add new overview comment for subpage metadata
V3 is now in for-next, targeting merge for 5.13. Please
On Mon, Mar 29, 2021 at 4:22 AM Bas Hulsken wrote:
>
> Dear list,
>
> due to a disk intermittently failing in my 4 disk array, I'm getting
> "transid verify failed" errors on my btrfs filesystem (see attached
> dmesg | grep -i btrfs dump in btrfs_dmesg.txt). When I run a scrub, the
> bad disk (/de
Hi Andrei,
On 2021-03-29 18:30, Andrei Borzenkov wrote:
On 29.03.2021 16:16, Claudius Heine wrote:
Hi,
I am currently investigating the possibility to use `btrfs-stream` files
(generated by `btrfs send`) for deploying a image based update to
systems (probably embedded ones).
One of the issues
Hi Martin,
On 2021-03-29 20:00, Martin Raiber wrote:
On 29.03.2021 19:25 Henning Schild wrote:
Am Mon, 29 Mar 2021 19:30:34 +0300
schrieb Andrei Borzenkov :
On 29.03.2021 16:16, Claudius Heine wrote:
Hi,
I am currently investigating the possibility to use `btrfs-stream`
files (generated by
Hi Claudius,
Le 29/03/2021 à 21:14, Claudius Heine a écrit :
> [...]
> Are you sure?
>
> I did a test with a 32MiB random file. I created one snapshot, then
> changed (not deleted or added) one byte in that file and then created
> a snapshot again. `btrfs send` created a >32MiB `btrfs-stream` file
--
*Compliments of SeasonGreetings from our Lord Jesus Christ
I have something to discuss with you and it is very important and urgent.
Please feel free to reach me on my e-mail:mrsayakaazu...@gmail.com
for further clarifications
Yours Sincerely Mrs Ayaka Azumi
On Mon, Mar 29, 2021 at 02:03:06PM +0200, Bas Hulsken wrote:
> Dear list,
> due to a disk intermittently failing in my 4 disk array, I'm getting
> "transid verify failed" errors on my btrfs filesystem (see attached
> dmesg | grep -i btrfs dump in btrfs_dmesg.txt).
Scary! But in this case, it lo
On Sun, Mar 28, 2021 at 9:41 AM B A wrote:
>
> * Samsung 840 series SSD (SMART data looks fine)
EVO or PRO? And what does its /proc/mounts line look like?
Total_LBAs_Written?
--
Chris Murphy
User reported that test fsck-tests/037-freespacetree-repair fails:
# TEST=037\* ./fsck-tests.sh
[TEST/fsck] 037-freespacetree-repair
btrfs check should have detected corruption
test failed for case 037-freespacetree-repair
The test tries to corrupt FST, call btrfs check readonly then repair
On 29.03.2021 22:14, Claudius Heine wrote:
> Hi Andrei,
>
> On 2021-03-29 18:30, Andrei Borzenkov wrote:
>> On 29.03.2021 16:16, Claudius Heine wrote:
>>> Hi,
>>>
>>> I am currently investigating the possibility to use `btrfs-stream` files
>>> (generated by `btrfs send`) for deploying a image base
On 30.03.2021 08:33, Andrei Borzenkov wrote:
> On 29.03.2021 22:14, Claudius Heine wrote:
>> Hi Andrei,
>>
>> On 2021-03-29 18:30, Andrei Borzenkov wrote:
>>> On 29.03.2021 16:16, Claudius Heine wrote:
Hi,
I am currently investigating the possibility to use `btrfs-stream` files
Unlike btrfs_file_extent_item, btrfs_ordered_extent has its length
limit (BTRFS_MAX_EXTENT_SIZE), which is far smaller than U32_MAX.
Using u64 for those length related members are just a waste of memory.
This patch will make the following members u32:
- num_bytes
- disk_num_bytes
- bytes_left
- t
On 30.03.21 г. 9:24, Wang Yugui wrote:
> Hi, Nikolay Borisov
>
> With a lot of dump_stack()/printk inserted around ENOMEM in btrfs code,
> we find out the call stack for ENOMEM.
> see the file -btrfs-dump_stack-when-ENOMEM.patch
>
>
> #cat /usr/hpc-bio/xfstests/results//generic/476.dmesg
36 matches
Mail list logo
