From: "Dejan Ribič" <dejan.ribic@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs resize partition problem
Date: Sat, 16 Nov 2013 21:37:09 +0100 [thread overview]
Message-ID: <5287D775.1090105@gmail.com> (raw)
Hello,
Originaly I had two seperate ext4 partitions for rootand home, thenI
recently converted my root ext4 partition to btrfs primarily because of
snapshots, I also created a subvolume for /var/cache/pacman/pkg because
I didn't want the packages in snapshots and that worked out great, I
have been running this setup without problems for two weeks now, but it
got me thinking why do I even have a seperate partition for home, so I
created a backup of my /home/stayerc directory and deleted the ext4
partition, but when I tried to resize btrfs partition using latest
gparted live cd, an error happened(details are on the bottom of email).
I would really apreciated any help.
Cheers,
Dejan
PS: Please Cc to me I am not subscribed
save-details from gparted:
---------------------------------------------
GParted 0.16.1 --enable-libparted-dmraid
Libparted 2.3
Move /dev/sda8 to the left and grow it from 20.95 GiB to 41.90 GiB
00:01:19 ( ERROR )
calibrate /dev/sda8 00:00:00 ( SUCCESS )
path: /dev/sda8
start: 1190326272
end: 1234257919
size: 43931648 (20.95 GiB)
check file system on /dev/sda8 for errors and (if possible) fix them
00:01:19 ( ERROR )
btrfsck /dev/sda8
Checking filesystem on /dev/sda8
UUID: 5f32176b-fa13-4af2-a5d9-ffbc558bdb13
free space inode generation (0) did not match free space cache
generation (1122)
free space inode generation (0) did not match free space cache
generation (1122)
free space inode generation (0) did not match free space cache
generation (1122)
free space inode generation (0) did not match free space cache
generation (1122)
free space inode generation (0) did not match free space cache
generation (1109)
found 3430820721 bytes used err is 19
total csum bytes: 7677820
total tree bytes: 569364480
total fs tree bytes: 529350656
total extent tree bytes: 29700096
btree space waste bytes: 161755833
file data blocks allocated: 38304477184
referenced 16981073920
Btrfs v0.20-rc1
checking extents
checking free space cache
checking fs roots
checking csums
There are no extents for csum range 0-69632
Csum exists for 0-69632 but there is no extent record
There are no extents for csum range 1121083392-1121087488
Csum exists for 1121083392-1121087488 but there is no extent record
There are no extents for csum range 1121099776-1121103872
Csum exists for 1121099776-1127346176 but there is no extent record
There are no extents for csum range 1127489536-1127493632
Csum exists for 1127489536-1127538688 but there is no extent record
There are no extents for csum range 1127550976-1127555072
Csum exists for 1127550976-1404313600 but there is no extent record
There are no extents for csum range 1404358656-1404362752
Csum exists for 1404358656-1404362752 but there is no extent record
There are no extents for csum range 1404375040-1404379136
Csum exists for 1404375040-1592889344 but there is no extent record
There are no extents for csum range 1954291712-1954295808
Csum exists for 1954291712-1970950144 but there is no extent record
There are no extents for csum range 1971093504-1971097600
Csum exists for 1971093504-2020798464 but there is no extent record
There are no extents for csum range 2021244928-2021249024
Csum exists for 2021244928-2021253120 but there is no extent record
There are no extents for csum range 2021699584-2021703680
Csum exists for 2021699584-2022080512 but there is no extent record
There are no extents for csum range 2022526976-2022531072
Csum exists for 2022526976-2277900288 but there is no extent record
There are no extents for csum range 2277912576-2277916672
Csum exists for 2277912576-2277916672 but there is no extent record
There are no extents for csum range 2277928960-2277933056
Csum exists for 2277928960-2277933056 but there is no extent record
There are no extents for csum range 2277945344-2277949440
Csum exists for 2277945344-2277949440 but there is no extent record
There are no extents for csum range 2277961728-2277965824
Csum exists for 2277961728-2277969920 but there is no extent record
There are no extents for csum range 2277982208-2277986304
Csum exists for 2277982208-2277986304 but there is no extent record
There are no extents for csum range 2277998592-2278002688
Csum exists for 2277998592-2278014976 but there is no extent record
There are no extents for csum range 2278027264-2278031360
Csum exists for 2278027264-2392010752 but there is no extent record
========================================
next reply other threads:[~2013-11-16 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 20:37 Dejan Ribič [this message]
2013-11-16 22:19 ` btrfs resize partition problem Duncan
2013-11-17 12:05 ` Russell Coker
2013-11-17 20:05 ` Duncan
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=5287D775.1090105@gmail.com \
--to=dejan.ribic@gmail.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;
as well as URLs for NNTP newsgroup(s).