On Thu, Aug 25, 2016 at 1:19 AM, Robert Munteanu
wrote:
> I've managed to capture one of the error messages,
> but via screenshot only.
And here's the full output below, via netconsole
[ 2806.245627] BTRFS error (device sda1): Duplicate entries in free
space cache, dumpi
(Replying to myself as I'm not subscribed and can't reply to Duncan's message)
Hi Duncan,
Good catch, mounting with -o skip_balance does allow me to mount the
disk properly.
Scrubbing the partition once mounted results in 0 errors.
I'm still going to keep this untouched for further investigatio
Hi,
Using Kernel 4.7.1 ( openSUSE Tumbleweed x86_64 ), btrfsprogs 4.7 I
always get a hard lockup when trying to mount my btrfs root partition.
This may be due to some previous errors which only manifested
themselves now, as it's been converted from an ext4 partition.
Using mount -o ro works. Usi
Hi,
I have a btrfs partition which exhibits some strange behaviours:
- btrfs scrub seems to force the filesystem in read-only mode
- transactions aborted with error -95
For context, this is a partition converted from ext4 which 'survived'
through the issues described at
http://www.spinics.net
On Fri, Aug 7, 2015 at 5:19 PM, David Sterba wrote:
> On Fri, Aug 07, 2015 at 05:17:34PM +0300, Robert Munteanu wrote:
>> Thanks for the update. Reading it looks to me like the patches should be at
>>
>>
>> http://repo.or.cz/w/btrfs-progs-unstable/devel.git/shortlog
On Fri, Aug 7, 2015 at 5:00 PM, David Sterba wrote:
> On Fri, Aug 07, 2015 at 04:05:44PM +0300, Robert Munteanu wrote:
>> >> Qu Wenruo (3):
>> >> btrfs-progs: fsck: Print correct file hole
>> >> btrfs-progs: fsck: Fix a infinite loop on discount file
>> Qu Wenruo (3):
>> btrfs-progs: fsck: Print correct file hole
>> btrfs-progs: fsck: Fix a infinite loop on discount file extent repair
>> btrfs-progs: fsck-tests: Add test case for inode lost all its file
>> extent
>
> Applied, thank you both.
I tried to find a git repo with these patc
On Mon, Aug 3, 2015 at 4:22 AM, Qu Wenruo wrote:
> Yes, you're right, that's a dead loop.
>
> But for better debugging, would you please upload the following info?
> 1) output of command "btrfs-debug-tree -t 5 ".
> The only important things are info about that inode.
> Whose objectid(first item in
On Fri, Jul 31, 2015 at 5:08 AM, Qu Wenruo wrote:
> Any full output about it?
Please see the attached log. I left the process running for about 4
hours, and after the first five minutes all it cared about was a
single inode. I ended up stopping it as it looks like it's not making
progress.
> Not
> The disk image (still) contains sensitive data so I can't share it
> unfortunately. What I can do is keep it untouched until Friday evening
> EEST and run any debugging commands that you might think of to trace
> down the source of the errors. Alternatively, if there's an easy and
> safe fix and
On Fri, Jul 10, 2015 at 3:34 AM, Qu Wenruo wrote:
> One of my patch addressed a problem that a converted btrfs can't pass
> btrfsck.
>
> Not sure if that is the cause, but if you can try btrfs-progs v3.19.1, the
> one without my btrfs-progs patches and some other newer convert related
> patches, a
On Wed, Jun 17, 2015 at 9:48 PM, Jeff Mahoney wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 6/12/15 8:19 AM, Robert Munteanu wrote:
>> Hi,
>>
>> I have converted my root ext4 partition to btrfs. I used an USB
>> stick to boot and used btrfs
On Wed, Jun 17, 2015 at 8:46 PM, Marc MERLIN wrote:
> On Fri, Jun 12, 2015 at 03:19:06PM +0300, Robert Munteanu wrote:
>> Hi,
>
> Note to others: kernel 4.0.4
>
> Reply to you:
> I tried ext4 to btrfs once a year ago and it severely mangled my
> filesystem.
> I looke
Hi,
I have converted my root ext4 partition to btrfs. I used an USB stick
to boot and used btrfs-convert.
I also did a balance and defrag ( in that order ) , both when the fs
was mounted.
After logging in to KDE I quickly get a read-only filesystem. I've
pasted the backtrace below
Jun 11 23:13:
14 matches
Mail list logo
