From: Roberto Spadim <roberto@spadim.com.br>
To: Shaohua Li <shli@kernel.org>
Cc: Holger Kiehl <Holger.Kiehl@dwd.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"neilb@suse.de" <neilb@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [patch 0/7] Add TRIM support for raid linear/0/1/10
Date: Tue, 13 Mar 2012 11:58:19 -0300 [thread overview]
Message-ID: <CABYL=To_A_n7K1SbUESSLi-vqb9TwPxaCQzxbneL+8bJ=kEcsA@mail.gmail.com> (raw)
In-Reply-To: <CANejiEWYCxY_hLwgyN08_cXC64c82irkNPytTjOpYyER7pTGow@mail.gmail.com>
could you send informations about yours devices? maybe a devices with
a diferent block sizes? are you running a virtual machine? a real one?
Em 13 de março de 2012 11:15, Shaohua Li <shli@kernel.org> escreveu:
> 2012/3/13 Holger Kiehl <Holger.Kiehl@dwd.de>:
>> On Tue, 13 Mar 2012, Shaohua Li wrote:
>>
>>> On 3/13/12 2:22 AM, Holger Kiehl wrote:
>>> > Hello,
>>> >
>>> > On Mon, 12 Mar 2012, Shaohua Li wrote:
>>> >
>>> >> The patches add TRIM support for raid linear/0/1/10. I'll add TRIM
>>> support for
>>> >> raid 4/5/6 later. The implementation is pretty straightforward and
>>> >> self-explained.
>>> >>
>>> > First, thanks for this patch!
>>> >
>>> > I have applied those patches against 3.3.0-rc7 and during boot the
>>> > kernel
>>> > reports a lot of the following:
>>> >
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611045] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18861064 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611047] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18862088 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611049] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18863112 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611052] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18864136 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611054] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18865160 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611056] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18866184 512
>>> Looks our SMTP server does something stupid. Sorry if you get two copies
>>> of the mail.
>>>
>>> Thanks for testing. Looks I fixed a sanity check in bio.c but there are
>>> similar check in raid0/10 which I forgot to fix. Below patch should fix
>>> it.
>>> please try.
>>>
>> Now I get following messages during boot (and it takes a very long time):
>>
>> Mar 13 10:23:25 c3po kernel: [ 251.355041] bio ffff88019e0abc70,
>> biotail ffff88019e0ddc00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.355052] request botched: dev sdb:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.355054] sector 52929353, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.355055] bio ffff88019e0aba70,
>> biotail ffff88019e0dda00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.355068] request botched: dev sdc:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.355069] sector 52929346, nr/cnr
>> 0/1016
>> Mar 13 10:23:25 c3po kernel: [ 251.355071] bio ffff88019e0aae00,
>> biotail ffff88019e0db380, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.373583] request botched: dev sda:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.373585] sector 52929354, nr/cnr
>> 0/1016
>> Mar 13 10:23:25 c3po kernel: [ 251.373587] bio ffff88019e0aba00,
>> biotail ffff88019e0ddc00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.373597] request botched: dev sdb:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.373599] sector 52929354, nr/cnr
>> 0/1016
>> Mar 13 10:23:25 c3po kernel: [ 251.373600] bio ffff88019e0ab800,
>> biotail ffff88019e0dda00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.373612] request botched: dev sdc:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.373614] sector 52929347, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.373616] bio ffff88019e0aaa70,
>> biotail ffff88019e0db380, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.392135] request botched: dev sda:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.392137] sector 52929355, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.392139] bio ffff88019e0ab670,
>> biotail ffff88019e0ddc00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.392150] request botched: dev sdb:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.392152] sector 52929355, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.392153] bio ffff88019e0ab470,
>> biotail ffff88019e0dda00, buffer (null), len 0
>>
>> After boot the system runs fine, but as soon as I do something (make clean
>> of
>> kernel tree with a sync) I get the same messages as above and it takes a
>> long time to sync:
>>
>> Mar 13 10:44:59 c3po kernel: [ 1550.740528] request botched: dev sda:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.740533] sector 12580617, nr/cnr
>> 0/776
>> Mar 13 10:44:59 c3po kernel: [ 1550.740537] bio ffff8801a362b670,
>> biotail ffff8801a30f3d80, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.747141] request botched: dev sdb:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.747144] sector 12579841, nr/cnr
>> 0/248
>> Mar 13 10:44:59 c3po kernel: [ 1550.747148] bio ffff88019e0dd200,
>> biotail ffff88019e0dd200, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.749429] request botched: dev sdc:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.749432] sector 12579841, nr/cnr
>> 0/248
>> Mar 13 10:44:59 c3po kernel: [ 1550.749436] bio ffff8801a362b600,
>> biotail ffff8801a362b600, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.755332] request botched: dev sda:
>> type=1, flags=916c081
>> Mar 13 10:44:59 c3po kernel: [ 1550.755335] sector 12580618, nr/cnr
>> 0/248
>> Mar 13 10:44:59 c3po kernel: [ 1550.755339] bio ffff8801a30f3d80,
>> biotail ffff8801a30f3d80, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.806832] request botched: dev sdb:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.806836] sector 12266497, nr/cnr
>> 0/1000
>> Mar 13 10:44:59 c3po kernel: [ 1550.806840] bio ffff8801a4dca800,
>> biotail ffff88019e0c9000, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.811972] request botched: dev sda:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.811976] sector 12266497, nr/cnr
>> 0/1000
>> Mar 13 10:44:59 c3po kernel: [ 1550.811979] bio ffff88019e0dd200,
>> biotail ffff8801a3794000, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.814081] request botched: dev sdc:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.814084] sector 12265497, nr/cnr 0/24
>> Mar 13 10:44:59 c3po kernel: [ 1550.814087] bio ffff8801a4dca870,
>> biotail ffff8801a37f4080, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.819150] request botched: dev sdc:
>> type=1, flags=916c081
>> Mar 13 10:44:59 c3po kernel: [ 1550.819153] sector 12265498, nr/cnr
>> 0/1000
>>
>> Please give me any hints what I can try next.
> Thanks for testing. This is very wield, the req->__data_len is wrong.
> Is this a clean build?
> didn't success to reproduce it, will check tomorrow again.
>
> Thanks,
> Shaohua
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Roberto Spadim <roberto@spadim.com.br>
To: Shaohua Li <shli@kernel.org>
Cc: Holger Kiehl <Holger.Kiehl@dwd.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"neilb@suse.de" <neilb@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [patch 0/7] Add TRIM support for raid linear/0/1/10
Date: Tue, 13 Mar 2012 11:58:19 -0300 [thread overview]
Message-ID: <CABYL=To_A_n7K1SbUESSLi-vqb9TwPxaCQzxbneL+8bJ=kEcsA@mail.gmail.com> (raw)
In-Reply-To: <CANejiEWYCxY_hLwgyN08_cXC64c82irkNPytTjOpYyER7pTGow@mail.gmail.com>
could you send informations about yours devices? maybe a devices with
a diferent block sizes? are you running a virtual machine? a real one?
Em 13 de março de 2012 11:15, Shaohua Li <shli@kernel.org> escreveu:
> 2012/3/13 Holger Kiehl <Holger.Kiehl@dwd.de>:
>> On Tue, 13 Mar 2012, Shaohua Li wrote:
>>
>>> On 3/13/12 2:22 AM, Holger Kiehl wrote:
>>> > Hello,
>>> >
>>> > On Mon, 12 Mar 2012, Shaohua Li wrote:
>>> >
>>> >> The patches add TRIM support for raid linear/0/1/10. I'll add TRIM
>>> support for
>>> >> raid 4/5/6 later. The implementation is pretty straightforward and
>>> >> self-explained.
>>> >>
>>> > First, thanks for this patch!
>>> >
>>> > I have applied those patches against 3.3.0-rc7 and during boot the
>>> > kernel
>>> > reports a lot of the following:
>>> >
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611045] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18861064 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611047] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18862088 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611049] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18863112 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611052] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18864136 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611054] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18865160 512
>>> > Mar 12 18:56:00 c3po kernel: [ 7.611056] md/raid0:md3: make_request bug:
>>> can't convert block across chunks or bigger than 512k 18866184 512
>>> Looks our SMTP server does something stupid. Sorry if you get two copies
>>> of the mail.
>>>
>>> Thanks for testing. Looks I fixed a sanity check in bio.c but there are
>>> similar check in raid0/10 which I forgot to fix. Below patch should fix
>>> it.
>>> please try.
>>>
>> Now I get following messages during boot (and it takes a very long time):
>>
>> Mar 13 10:23:25 c3po kernel: [ 251.355041] bio ffff88019e0abc70,
>> biotail ffff88019e0ddc00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.355052] request botched: dev sdb:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.355054] sector 52929353, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.355055] bio ffff88019e0aba70,
>> biotail ffff88019e0dda00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.355068] request botched: dev sdc:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.355069] sector 52929346, nr/cnr
>> 0/1016
>> Mar 13 10:23:25 c3po kernel: [ 251.355071] bio ffff88019e0aae00,
>> biotail ffff88019e0db380, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.373583] request botched: dev sda:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.373585] sector 52929354, nr/cnr
>> 0/1016
>> Mar 13 10:23:25 c3po kernel: [ 251.373587] bio ffff88019e0aba00,
>> biotail ffff88019e0ddc00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.373597] request botched: dev sdb:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.373599] sector 52929354, nr/cnr
>> 0/1016
>> Mar 13 10:23:25 c3po kernel: [ 251.373600] bio ffff88019e0ab800,
>> biotail ffff88019e0dda00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.373612] request botched: dev sdc:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.373614] sector 52929347, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.373616] bio ffff88019e0aaa70,
>> biotail ffff88019e0db380, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.392135] request botched: dev sda:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.392137] sector 52929355, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.392139] bio ffff88019e0ab670,
>> biotail ffff88019e0ddc00, buffer (null), len 0
>> Mar 13 10:23:25 c3po kernel: [ 251.392150] request botched: dev sdb:
>> type=1, flags=916c081
>> Mar 13 10:23:25 c3po kernel: [ 251.392152] sector 52929355, nr/cnr 0/8
>> Mar 13 10:23:25 c3po kernel: [ 251.392153] bio ffff88019e0ab470,
>> biotail ffff88019e0dda00, buffer (null), len 0
>>
>> After boot the system runs fine, but as soon as I do something (make clean
>> of
>> kernel tree with a sync) I get the same messages as above and it takes a
>> long time to sync:
>>
>> Mar 13 10:44:59 c3po kernel: [ 1550.740528] request botched: dev sda:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.740533] sector 12580617, nr/cnr
>> 0/776
>> Mar 13 10:44:59 c3po kernel: [ 1550.740537] bio ffff8801a362b670,
>> biotail ffff8801a30f3d80, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.747141] request botched: dev sdb:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.747144] sector 12579841, nr/cnr
>> 0/248
>> Mar 13 10:44:59 c3po kernel: [ 1550.747148] bio ffff88019e0dd200,
>> biotail ffff88019e0dd200, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.749429] request botched: dev sdc:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.749432] sector 12579841, nr/cnr
>> 0/248
>> Mar 13 10:44:59 c3po kernel: [ 1550.749436] bio ffff8801a362b600,
>> biotail ffff8801a362b600, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.755332] request botched: dev sda:
>> type=1, flags=916c081
>> Mar 13 10:44:59 c3po kernel: [ 1550.755335] sector 12580618, nr/cnr
>> 0/248
>> Mar 13 10:44:59 c3po kernel: [ 1550.755339] bio ffff8801a30f3d80,
>> biotail ffff8801a30f3d80, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.806832] request botched: dev sdb:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.806836] sector 12266497, nr/cnr
>> 0/1000
>> Mar 13 10:44:59 c3po kernel: [ 1550.806840] bio ffff8801a4dca800,
>> biotail ffff88019e0c9000, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.811972] request botched: dev sda:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.811976] sector 12266497, nr/cnr
>> 0/1000
>> Mar 13 10:44:59 c3po kernel: [ 1550.811979] bio ffff88019e0dd200,
>> biotail ffff8801a3794000, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.814081] request botched: dev sdc:
>> type=1, flags=9164081
>> Mar 13 10:44:59 c3po kernel: [ 1550.814084] sector 12265497, nr/cnr 0/24
>> Mar 13 10:44:59 c3po kernel: [ 1550.814087] bio ffff8801a4dca870,
>> biotail ffff8801a37f4080, buffer (null), len 0
>> Mar 13 10:44:59 c3po kernel: [ 1550.819150] request botched: dev sdc:
>> type=1, flags=916c081
>> Mar 13 10:44:59 c3po kernel: [ 1550.819153] sector 12265498, nr/cnr
>> 0/1000
>>
>> Please give me any hints what I can try next.
> Thanks for testing. This is very wield, the req->__data_len is wrong.
> Is this a clean build?
> didn't success to reproduce it, will check tomorrow again.
>
> Thanks,
> Shaohua
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
next prev parent reply other threads:[~2012-03-13 14:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 3:04 [patch 0/7] Add TRIM support for raid linear/0/1/10 Shaohua Li
2012-03-12 3:04 ` [patch 1/7] block: makes bio_split support bio without data Shaohua Li
2012-03-12 3:04 ` [patch 2/7] md: linear supports TRIM Shaohua Li
2012-03-12 3:04 ` [patch 3/7] md: raid 0 " Shaohua Li
2012-03-12 3:04 ` [patch 4/7] md: raid 1 " Shaohua Li
2012-03-12 3:04 ` [patch 5/7] md: raid 10 " Shaohua Li
2012-03-12 3:04 ` [patch 6/7] blk: add plug for blkdev_issue_discard Shaohua Li
2012-03-13 15:51 ` Vivek Goyal
2012-03-13 15:51 ` Vivek Goyal
2012-03-13 17:04 ` Martin K. Petersen
2012-03-13 17:14 ` Vivek Goyal
2012-03-13 17:19 ` Martin K. Petersen
2012-03-12 3:04 ` [patch 7/7] blk: use correct sectors limitation for discard request Shaohua Li
2012-03-13 16:00 ` Vivek Goyal
2012-03-13 16:00 ` Vivek Goyal
2012-03-12 3:18 ` [patch 0/7] Add TRIM support for raid linear/0/1/10 Roberto Spadim
2012-03-12 3:18 ` Roberto Spadim
2012-03-12 18:22 ` Holger Kiehl
[not found] ` <4F5EFEB6.4060402@kernel.org>
2012-03-13 12:22 ` Holger Kiehl
2012-03-13 14:15 ` Shaohua Li
2012-03-13 14:15 ` Shaohua Li
2012-03-13 14:58 ` Roberto Spadim [this message]
2012-03-13 14:58 ` Roberto Spadim
2012-03-13 15:44 ` Holger Kiehl
2012-03-14 1:30 ` Shaohua Li
2012-03-14 10:25 ` Holger Kiehl
2012-03-14 11:14 ` Shaohua Li
2012-03-14 11:14 ` Shaohua Li
2012-03-14 11:32 ` Shaohua Li
2012-03-14 21:01 ` Holger Kiehl
2012-03-14 21:13 ` Holger Kiehl
2012-03-15 2:39 ` Shaohua Li
2012-03-15 9:08 ` Holger Kiehl
2012-03-16 2:19 ` Shaohua Li
[not found] ` <4F5EA8E9.5010502@fusionio.com>
2012-03-14 2:25 ` NeilBrown
2012-03-14 2:25 ` NeilBrown
2012-03-14 2:24 ` NeilBrown
2012-03-14 2:47 ` Shaohua Li
2012-03-17 18:14 ` Mark Lord
2012-03-18 2:03 ` Shaohua Li
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='CABYL=To_A_n7K1SbUESSLi-vqb9TwPxaCQzxbneL+8bJ=kEcsA@mail.gmail.com' \
--to=roberto@spadim.com.br \
--cc=Holger.Kiehl@dwd.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@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 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.