From: Anand Jain <Anand.Jain@oracle.com>
To: Paul Jones <paul@pauljones.id.au>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs check - Couldn't open file system
Date: Tue, 04 Nov 2014 11:13:42 +0800 [thread overview]
Message-ID: <54584466.1030007@oracle.com> (raw)
In-Reply-To: <54584403.1080501@oracle.com>
On 11/04/2014 11:12 AM, Anand Jain wrote:
>
> very strange. I have no clue, yet. also bit concerned if this
> turns out to be a real issue. hope you could help to narrow down.
>
> can you send `blkid` output from your system.
> And
> can you go back to 3.16 and check if you have the same issue.
I mean 3.16 btrfs-progs only.
> thanks, anand
>
>
>> IWT-VM ~ # uname -a
>> Linux IWT-VM 3.17.2-gentoo #1 SMP Mon Nov 3 15:46:50 AEDT 2014 x86_64
>> Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz GenuineIntel GNU/Linux
>> IWT-VM ~ # mount
>> /dev/sdb2 on / type btrfs
>> (rw,noatime,compress=zlib,ssd,noacl,space_cache)
>> /dev/sdh1 on /media/fast type btrfs (rw,noatime,ssd,noacl,space_cache)
>> /dev/sdg3 on /media/backup type btrfs
>> (rw,noatime,compress=zlib,noacl,space_cache)
>> /dev/sda1 on /media/data type btrfs
>> (rw,noatime,compress=zlib,noacl,space_cache)
>> IWT-VM ~ # btrfs fi sh
>> Label: 'Root' uuid: 61f6ce80-6d05-414f-9f0f-3d540fa82f2e
>> Total devices 2 FS bytes used 6.58GiB
>> devid 4 size 60.00GiB used 18.03GiB path /dev/sdb2
>> devid 5 size 59.93GiB used 18.03GiB path /dev/sdi3
>>
>> Label: 'Fast' uuid: c41dc6db-6f00-4d60-a2f7-acbceb25e4e7
>> Total devices 3 FS bytes used 396.85GiB
>> devid 1 size 471.93GiB used 416.02GiB path /dev/sdh1
>> devid 2 size 412.00GiB used 356.01GiB path /dev/sdi1
>> devid 3 size 163.57GiB used 108.01GiB path /dev/sdb1
>>
>> Label: 'Backup' uuid: 92162be2-e52f-42fe-a9fd-da4f26c6abd1
>> Total devices 5 FS bytes used 2.74TiB
>> devid 6 size 891.50GiB used 822.00GiB path /dev/sdg3
>> devid 8 size 698.64GiB used 629.00GiB path /dev/sdd1
>> devid 9 size 891.51GiB used 821.03GiB path /dev/sde3
>> devid 10 size 2.73TiB used 2.66TiB path /dev/sdc1
>> devid 11 size 931.51GiB used 924.00GiB path /dev/sdf1
>>
>> Label: 'Data' uuid: 89181f84-bace-43f8-9534-693f99c4d033
>> Total devices 2 FS bytes used 42.50GiB
>> devid 1 size 279.46GiB used 211.03GiB path /dev/sda1
>> devid 2 size 279.46GiB used 211.03GiB path /dev/sdj1
>>
>> Btrfs v3.17
>> IWT-VM ~ # umount /media/backup
>> umount: /media/backup: not mounted
>> IWT-VM ~ # btrfs check /dev/sdg3
>> Couldn't open file system
>> IWT-VM ~ # btrfs check /dev/sdd1
>> Couldn't open file system
>> IWT-VM ~ # btrfs check /dev/sde3
>> Couldn't open file system
>> IWT-VM ~ # btrfs check /dev/sda1
>> Checking filesystem on /dev/sda1
>> UUID: 89181f84-bace-43f8-9534-693f99c4d033
>> checking extents
>> checking free space cache
>> checking fs roots
>> checking csums
>> checking root refs
>> found 38060448123 bytes used err is 0
>> total csum bytes: 44401072
>> total tree bytes: 110723072
>> total fs tree bytes: 50872320
>> total extent tree bytes: 9994240
>> btree space waste bytes: 12145264
>> file data blocks allocated: 45618331648
>> referenced 48120782848
>> Btrfs v3.17
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-04 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 10:00 btrfs check - Couldn't open file system Paul Jones
2014-11-04 3:12 ` Anand Jain
2014-11-04 3:13 ` Anand Jain [this message]
2014-11-04 3:27 ` Paul Jones
2014-11-04 5:34 ` Anand Jain
2014-11-04 5:35 ` Paul Jones
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=54584466.1030007@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=paul@pauljones.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.