public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Michael Lyle <mlyle@lyle.org>, Coly Li <i@coly.li>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: ont out of 6 bcache devices does not register automatically
Date: Wed, 22 Nov 2017 22:10:48 +0100	[thread overview]
Message-ID: <32714083-db95-0837-5dcd-e863a833b89d@profihost.ag> (raw)
In-Reply-To: <0387447a-cce1-4162-3458-03193e146732@lyle.org>


Am 22.11.2017 um 22:03 schrieb Michael Lyle:
> On 11/22/2017 12:56 PM, Stefan Priebe - Profihost AG wrote:
>>
>> Am 22.11.2017 um 21:44 schrieb Michael Lyle:
>>> On 11/22/2017 12:36 PM, Stefan Priebe - Profihost AG wrote:
>>>> Am 22.11.2017 um 21:22 schrieb Michael Lyle:
>>> mlyle@midnight:~/Downloads$ blkid 8k
>>> 8k: UUID="65811163-4ffc-4823-ad72-bae10ce85b63" TYPE="bcache"
>>> mlyle@midnight:~/Downloads$ blkid --version
>>> blkid from util-linux 2.30.1  (libblkid 2.30.1, 20-Jul-2017)
>>>
>>> I don't understand, it seems OK.
>> i think i remember that the xfs external log superblock is NOT at the
>> beginning. Not sure where it is and yes there's an XFS on top of bcache...
>>
>> Greets,
>> Stefan
> 
> It shouldn't be an issue because: A) blkid should "favor" bcache, and B)
> the other filesystem data structures should be offset and not at the
> position that blkid will be looking for them.  Can you check your blkid
> version?

If you strace blkid you see that it seeks several positions and reads them.

Exmaple:
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
lseek(3, 0, SEEK_SET)                   = 0
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
lseek(3, 1024, SEEK_SET)                = 1024
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
lseek(3, 1048576, SEEK_SET)             = 1048576
read(3,
"ABTB\0\0\1\36\0\0\1\310\0\0\0\215\0029\335\334\0\0\0070\0029\355\f\0\0\4\0"...,
1024) = 1024
lseek(3, 3072, SEEK_SET)                = 3072
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
lseek(3, 7168, SEEK_SET)                = 7168
read(3,
"\0\0\232\352\0\0\0\26\0\0\233\301\0\0\0\20\0\0\234\21\0\0\0\34\0\0\234.\0\0\0\1"...,
1024) = 1024
lseek(3, 15360, SEEK_SET)               = 15360
read(3,
"\0\0'\353\0\0\0\1\0\0'\353\0\0\0\1\0\0'\353\0\0\0\1\0\0'\353\0\0\0\1"...,
1024) = 1024
lseek(3, 31744, SEEK_SET)               = 31744
read(3,
"\0\10\340\346\0\0\0\30\0\10\340\346\0\0\0\30drmtwsS0l\n1gKn80"...,
1024) = 1024
lseek(3, 64512, SEEK_SET)               = 64512
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
lseek(3, 0, SEEK_SET)                   = 0
mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7efe60612000
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
262144) = 262144
lseek(3, 393216, SEEK_SET)              = 393216

> 
> Mike
> --
> 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
> 

  parent reply	other threads:[~2017-11-22 21:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 11:23 ont out of 6 bcache devices does not register automatically Stefan Priebe - Profihost AG
2017-11-22 12:16 ` Coly Li
2017-11-22 12:26   ` Stefan Priebe - Profihost AG
2017-11-22 12:57     ` Coly Li
2017-11-22 13:14       ` Stefan Priebe - Profihost AG
2017-11-22 13:29         ` Coly Li
2017-11-22 14:16           ` Stefan Priebe - Profihost AG
2017-11-22 15:51             ` Coly Li
2017-11-22 19:07               ` Stefan Priebe - Profihost AG
2017-11-22 17:51         ` Michael Lyle
2017-11-22 19:06           ` Stefan Priebe - Profihost AG
2017-11-22 19:42             ` Stefan Priebe - Profihost AG
2017-11-22 20:22               ` Michael Lyle
2017-11-22 20:36                 ` Stefan Priebe - Profihost AG
2017-11-22 20:44                   ` Michael Lyle
2017-11-22 20:56                     ` Stefan Priebe - Profihost AG
2017-11-22 21:03                       ` Michael Lyle
2017-11-22 21:07                         ` Stefan Priebe - Profihost AG
2017-11-22 21:10                           ` Michael Lyle
2017-11-22 21:13                             ` Stefan Priebe - Profihost AG
2017-11-23  7:10                               ` Stefan Priebe - Profihost AG
2017-11-28  9:36                                 ` Stefan Priebe - Profihost AG
     [not found]                                   ` <CAJ+L6qc79S1t10WfeycRFLesuqbZNfUXrN7qo6fVuwbHk=n8xw@mail.gmail.com>
2017-11-28 19:32                                     ` Stefan Priebe - Profihost AG
2017-11-28 19:51                                       ` Michael Lyle
2017-11-28 19:59                                         ` Stefan Priebe - Profihost AG
2017-11-28 20:05                                           ` Michael Lyle
2017-11-28 20:31                                             ` Stefan Priebe - Profihost AG
2017-12-01 15:10                                               ` Nix
2017-12-10 19:34                                                 ` Stefan Priebe - Profihost AG
2017-12-10 19:36                                                   ` Michael Lyle
2017-12-10 19:39                                                     ` Stefan Priebe - Profihost AG
2017-12-12 15:38                                                     ` Nix
2017-11-22 21:10                         ` Stefan Priebe - Profihost AG [this message]
2017-11-22 21:13                           ` Michael Lyle
2017-11-23 11:43               ` Kai Krakow
2017-11-23 12:03                 ` Stefan Priebe - Profihost AG

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=32714083-db95-0837-5dcd-e863a833b89d@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=i@coly.li \
    --cc=linux-bcache@vger.kernel.org \
    --cc=mlyle@lyle.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