On Tue, Mar 30, 2021 at 6:50 AM Hendrik Friedel wrote:
> > Next
> >'btrfs check --readonly' (must be done offline ie booted from usb
> >stick). And if it all comes up without errors or problems, you can
> >zero the statistics with 'btrfs dev stats -z'.
> No error found. Neither in btrfs check, n
I'm going to fill in some details from the multiday conversation with
IRC regulars. We couldn't figure out a way forward.
* WDC Red with Firmware Version: 80.00A80, which is highly suspected
to deal with power fail and write caching incorrectly, and at least on
Btrfs apparently pretty much always
> -Original Message-
> From: Ritesh Harjani
> Sent: Tuesday, March 23, 2021 11:48 PM
> Subject: Re: [PATCH v3 02/10] fsdax: Factor helper: dax_fault_actor()
>
>
>
> On 3/19/21 7:22 AM, Shiyang Ruan wrote:
> > The core logic in the two dax page fault functions is similar. So,
> > move
On Tue, Mar 30, 2021 at 08:05:56PM +0200, Markus Schaaf wrote:
> Hi all,
>
> on one of my machines I'm seeing these warnings a lot lately:
>
> [ cut here ]
> WARNING: CPU: 1 PID: 314 at fs/fs-writeback.c:2472
> __writeback_inodes_sb_nr+0xb8/0xd0
> Modules linked in: iTCO_
On Tue, Mar 30, 2021 at 07:20:14PM +0200, Bas Hulsken wrote:
> On Tue, 2021-03-30 at 11:46 -0400, Zygo Blaxell wrote:
> > On Tue, Mar 30, 2021 at 03:01:57PM +0200, Bas Hulsken wrote:
> > > I followed your advice, Zygo and Chris, and did both:
> > > 1) smartctl -l scterc,70,70 /dev/sdX for all 4 dri
On Tue, Mar 30, 2021 at 10:12:40AM +0200, Claudius Heine wrote:
> Hi Andrei,
>
> On 2021-03-30 07:38, Andrei Borzenkov wrote:
> > 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
Hello,
if anyone can help me with the problem above?
Have tried a Photorec (even if i know the chance are really poor), and
have got some non-sens files, lkie pdf of 2Gb, most of them are
unusable, except smal size file, like jpg pic...
thanks for any help.
Thierry
Le sam. 27 mars 2021 à 12
From: Nick Terrell
Adds decompress_sources.h which includes every .c file necessary for
zstd decompression. This is used in decompress_unzstd.c so the internal
structure of the library isn't exposed.
This allows us to upgrade the zstd library version without modifying any
callers. Instead we jus
From: Nick Terrell
This patch:
- Moves `include/linux/zstd.h` -> `include/linux/zstd_lib.h`
- Updates modified zstd headers to yearless copyright
- Adds a new API in `include/linux/zstd.h` that is functionally
equivalent to the in-use subset of the current API. Functions are
renamed to avoid
From: Nick Terrell
Please pull from
g...@github.com:terrelln/linux.git tags/v9-zstd-1.4.10
to get these changes. Alternatively the patchset is included.
This patchset upgrades the zstd library to the latest upstream release. The
current zstd version in the kernel is a modified version of ups
On Thu, Mar 25, 2021 at 01:08:02PM +0100, David Sterba wrote:
On Thu, Mar 25, 2021 at 07:24:41AM -0400, Sasha Levin wrote:
From: Qu Wenruo
[ Upstream commit fbf48bb0b197e6894a04c714728c952af7153bf3 ]
There is a piece of weird code in insert_prealloc_file_extent(), which
looks like:
r
On Tue, Mar 30, 2021 at 2:44 AM B A wrote:
>
>
> > Gesendet: Dienstag, 30. März 2021 um 00:07 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
Hi all,
on one of my machines I'm seeing these warnings a lot lately:
[ cut here ]
WARNING: CPU: 1 PID: 314 at fs/fs-writeback.c:2472
__writeback_inodes_sb_nr+0xb8/0xd0
Modules linked in: iTCO_wdt wireguard curve25519_x86_64 libchacha20poly1305
intel_pmc_bxt iTCO_vendor
ping?
On Sun, Mar 21, 2021 at 09:03:11PM +, Matthew Wilcox (Oracle) wrote:
> Implement readahead_batch_length() to determine the number of bytes in
> the current batch of readahead pages and use it in btrfs.
>
> Signed-off-by: Matthew Wilcox (Oracle)
> ---
> fs/btrfs/extent_io.c| 6 ++--
On Tue, 2021-03-30 at 11:46 -0400, Zygo Blaxell wrote:
> On Tue, Mar 30, 2021 at 03:01:57PM +0200, Bas Hulsken wrote:
> > I followed your advice, Zygo and Chris, and did both:
> > 1) smartctl -l scterc,70,70 /dev/sdX for all 4 drives in the array
> > (the
> > drives do support this)
> > 2) echo 180
Am Tue, 30 Mar 2021 10:12:40 +0200
schrieb Claudius Heine :
> Hi Andrei,
>
> On 2021-03-30 07:38, Andrei Borzenkov wrote:
> > 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 Tue, Mar 30, 2021 at 03:01:57PM +0200, Bas Hulsken wrote:
> I followed your advice, Zygo and Chris, and did both:
> 1) smartctl -l scterc,70,70 /dev/sdX for all 4 drives in the array (the
> drives do support this)
> 2) echo 180 > /sys/block/sdX/device/timeout for all 4 drives
>
> with that I at
On Tue, Mar 23, 2021 at 11:53 AM David Sterba wrote:
>
> On Wed, Mar 17, 2021 at 04:01:43PM -0400, Neal Gompa wrote:
> > This is a patch requesting all substantial copyright owners to sign off
> > on changing the license of the libbtrfsutil code to LGPLv2.1+ in order
> > to resolve various concern
Hello,
thanks for your reply, Chris.
[Mo Mär 29 09:29:22 2021] BTRFS info (device sda1): bdev /dev/sda1 errs:
wr 133, rd 133, flush 0, corrupt 0, gen 1
Maybe, the last line is concerning?
Yes. Do a 'btrfs scrub' and check dmesg for detailed errors.
[Mo Mär 29 09:29:22 2021] BTRFS info (d
Fix the following whitescan warning:
Calling "zlib_inflateEnd(&workspace->strm)" is only useful for its
return value, which is ignored.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
fs/btrfs/zlib.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/btrfs/zlib.c b/fs/btrfs/zlib.c
> Gesendet: Dienstag, 30. März 2021 um 00:07 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:
> >
> > * Samsung 840 series SSD (SMART data looks fine)
>
> EV
Hi Andrei,
On 2021-03-30 07:38, Andrei Borzenkov wrote:
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 possibilit
Hi Lionel,
On 2021-03-29 21:53, Lionel Bouton wrote:
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. `bt
H,
> 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/
24 matches
Mail list logo
