.10.2019, 14:18 -0600 schrieb Chris Murphy:
> On Thu, Oct 3, 2019 at 6:18 AM Robert Krig
> wrote:
> > By the way, how serious is the error I've encountered?
> > I've run a second scrub in the meantime, it aborted when it came
> > close
> > to the end, just
By the way, how serious is the error I've encountered?
I've run a second scrub in the meantime, it aborted when it came close
to the end, just like the first time.
If the files that are corrupt have been deleted is this error going to
go away?
On Mi, 2019-10-02 at 12:17 +0200, R
.10.2019, 12:10 -0600 schrieb Chris Murphy:
> On Mon, Sep 30, 2019 at 3:37 AM Robert Krig
> wrote:
> > I've upgraded to btrfs-progs v5.2.1
> > Here is the output from btrfs check -p --readonly /dev/sda
> >
> >
> > Opening filesystem to check...
> > Che
+0300 schrieb Nikolay Borisov:
>
> On 30.09.19 г. 0:38 ч., Robert Krig wrote:
> > Hi guys. First off, I've got backups so no worries there. I'm just
> > trying to understand what's happening and which files are affected.
> > I've got a scrub running and t
Hi guys. First off, I've got backups so no worries there. I'm just
trying to understand what's happening and which files are affected.
I've got a scrub running and the kernel dmesg buffer spit out the
following:
BTRFS warning (device sda): checksum/header error at logical
48781340082176 on dev /de
Hi guys.
I was wondering, are there any recommended best practices when using
Raid5/6 on BTRFS?
I intend to build a 4 Disk BTRFS Raid5 array, but that's just going to
be as a backup for my main ZFS Server. So the data on it is not
important. I just want to see how RAID5 will behave over time.
Th
On 04.04.2017 18:55, Chris Murphy wrote:
> On Tue, Apr 4, 2017 at 10:52 AM, Chris Murphy wrote:
>
>
>> Mounting -o ro,degraded is probably permitted by the file system, but
>> chunks of the file system and certainly your data, will be missing. So
>> it's just a matter of time before copying data
On 03.04.2017 16:25, Robert Krig wrote:
>
> I'm gonna run a extensive memory check once I get home, since you
> mentioned corrupt memory might be an issue here.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a mes
On 03.04.2017 16:20, Robert Krig wrote:
>
> On 03.04.2017 16:08, Hans van Kranenburg wrote:
>> On 04/03/2017 12:11 PM, Robert Krig wrote:
>> The corruption is at item 157. Can you attach all of the output, or
>> pastebin it?
>>
>
> I've attached the
On 03.04.2017 16:08, Hans van Kranenburg wrote:
> On 04/03/2017 12:11 PM, Robert Krig wrote:
> The corruption is at item 157. Can you attach all of the output, or
> pastebin it?
>
I've attached the entire log of btrfs-debug-tree. This was generated
with btrfs-progs 4.7
On 03.04.2017 12:11, Robert Krig wrote:
> Hi guys, I seem to have run into a spot of trouble with my btrfs partition.
>
> I've got 4 x 8TB in a RAID1 BTRFS configuration.
>
> I'm running Debian Jessie 64 Bit, 4.9.0-0.bpo.2-amd64 kernel. Btrfs
> progs version v4.7
Hi guys, I seem to have run into a spot of trouble with my btrfs partition.
I've got 4 x 8TB in a RAID1 BTRFS configuration.
I'm running Debian Jessie 64 Bit, 4.9.0-0.bpo.2-amd64 kernel. Btrfs
progs version v4.7.3
Server has 8GB of Ram.
I was running duperemove using a hashfile, which seemed t
ssume you have git installed:
>
> git clone
> https://gitlab.wellbehavedsoftware.com/well-behaved-software/btrfs-dedupe.git
>
> Then cd in and build using cargo:
>
> cd btrfs-dedupe
> cargo build --release
>
> There is basically just one binary which will end up in
&
Hi, could you include some build instructions for people that are
unfamiliar with compiling rust code?
On 08.01.2017 17:57, James Pharaoh wrote:
> Hi everyone,
>
> I'm pleased to announce a new version of my btrfs-dedupe tool, written
> in rust, available here:
>
> http://btrfs-dedupe.com/
>
> Bi
As Chris mentioned, check out the Bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=93581
I have a 8TB SMR Drive and the kernel was reporting drive errors.
Switching to Kernel 3.16 (Standard Debian Jessie kernel) fixed it for me
( for the moment).
>From what I read in that kernel bug
a while for patches to the
mailing list to be merged into one of the repos.
What would be the easiest way for me to compile that specific patch?
Which kernel version sources do I ideally need?
Is there a git repo that already has that patch included?
Thank you for your help.
On 10.11.2015 11
Hi,
I'm running Kernel 4.3 and Btrfs-tools 4.3 on Debian Jessie. I compiled
the tools and kernel myself.
Recently I added a new disk to my btrfs volume and wanted to proceed to
convert from single to raid1.
Unfortunately the new disk seems to be faulty and started throwing a lot
of errors.
The b
Hi, I was wondering.
What exactly is contained in btrfs metadata?
I've read about some users setting up their btrfs volumes as
data=single, but metadata=raid1
Is there any actual benefit to that? I mean, if you keep your data as
single, but have multiple copies of metadata, does that still allow
Hi.
I have an Old Server with a bunch of btrfs Snapshots.
I'm setting up a new server and I would like to transfer those Snapshots
as efficiently as possible, while still maintaining their parent<->child
relationships for space efficient storage.
Apart from manually using "btrfs send" and "btrfs
19 matches
Mail list logo
