From: Killian De Volder <killian.de.volder@megasoft.be>
To: linux-bcache@vger.kernel.org
Subject: Re: bcache wont register cache and attempt to access beyond end of device
Date: Wed, 05 Aug 2015 15:03:59 +0200 [thread overview]
Message-ID: <55C209BF.1020708@megasoft.be> (raw)
In-Reply-To: <CAOOKTyBAb4H1COk4-zmamsR4i4G+oomDQfR7W4vG3opx7mS+6w@mail.gmail.com>
If I am not mistaking you have to register the CUID of the chache device.
Not the block device. (Or it has been fixed.)
Killian De Volder
On 05-08-15 14:52, Георгий Стариков wrote:
> Hello,
> bcache worked fine until i rebooted server. Now, bcache wont register
> cache device. Backing registered successfully.
> Is there a way to fix it?
> Configuration was : cache - sdc, backing - md0 (md raid6)
>
> Details:
>
> # echo /dev/sdc > /sys/fs/bcache/register
>
> dmesg
> [ 1004.580163] bcache: prio_read() bad csum reading priorities
> [ 1004.580167] bcache: prio_read() bad magic reading priorities
> [ 1004.580497] attempt to access beyond end of device
> [ 1004.580499] sdc: rw=48, want=12989067124903043072, limit=468862128
> [ 1004.580501] bcache: error on 4ca0fbc9-d20b-4a3d-bbd1-38d9a5810c27:
> accessing priorities, disabling caching
> [ 1004.582053] bcache: prio_read() bad csum reading priorities
> [ 1004.582055] bcache: prio_read() bad magic reading priorities
> [ 1004.582395] attempt to access beyond end of device
> [ 1004.582397] sdc: rw=48, want=12989067124903043072, limit=468862128
> [ 1004.583942] bcache: prio_read() bad csum reading priorities
> [ 1004.583944] bcache: prio_read() bad magic reading priorities
> [ 1004.584997] bcache: register_cache() registered cache device sdc
> [ 1004.585504] bcache: cache_set_free() Cache set
> 4ca0fbc9-d20b-4a3d-bbd1-38d9a5810c27 unregistered
>
> # bcache-super-show /dev/sdc
> sb.magic ok
> sb.first_sector 8 [match]
> sb.csum 44826230D24195E8 [match]
> sb.version 3 [cache device]
>
> dev.label (empty)
> dev.uuid cd4241f5-1271-4a1a-a530-58d3ccc2f97e
> dev.sectors_per_block 1
> dev.sectors_per_bucket 1024
> dev.cache.first_sector 1024
> dev.cache.cache_sectors 468860928
> dev.cache.total_sectors 468861952
> dev.cache.ordered yes
> dev.cache.discard yes
> dev.cache.pos 0
> dev.cache.replacement 0 [lru]
>
> cset.uuid 4ca0fbc9-d20b-4a3d-bbd1-38d9a5810c27
>
> # bcache-super-show /dev/md0
> sb.magic ok
> sb.first_sector 8 [match]
> sb.csum F3A7C3593D24C25A [match]
> sb.version 1 [backing device]
>
> dev.label (empty)
> dev.uuid 80bdbcce-f1e1-4af9-a2bd-e4be24067fc5
> dev.sectors_per_block 1
> dev.sectors_per_bucket 1024
> dev.data.first_sector 16
> dev.data.cache_mode 1 [writeback]
> dev.data.cache_state 1 [clean]
>
> cset.uuid 4ca0fbc9-d20b-4a3d-bbd1-38d9a5810c27
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" 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:[~2015-08-05 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 12:52 bcache wont register cache and attempt to access beyond end of device Георгий Стариков
2015-08-05 13:03 ` Killian De Volder [this message]
2015-08-05 14:23 ` Георгий Стариков
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=55C209BF.1020708@megasoft.be \
--to=killian.de.volder@megasoft.be \
--cc=linux-bcache@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