From: Wols Lists <antlists@youngman.org.uk>
To: Liwei <xieliwei@gmail.com>, Weedy <weedy2887@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Buffer I/O error... async page read
Date: Wed, 7 Feb 2018 14:54:20 +0000 [thread overview]
Message-ID: <5A7B131C.1010102@youngman.org.uk> (raw)
In-Reply-To: <CAPE0SYzi53vnV-rPtRcfqphpO-KTNwEuP+3yYcsk+Cmu9p-hGg@mail.gmail.com>
On 07/02/18 07:02, Liwei wrote:
> I was referring to the metadata formats
> "https://raid.wiki.kernel.org/index.php/RAID_superblock_formats" page
> while trying to figure things out and noticed that it too is outdated.
> I'm willing to help update the wiki in whatever ways I can if someone
> can approve my account.
I think your account is probably all set up and working. There's just a
magic formula to getting it activated :-) Ask for a password reset :-)
And please don't edit that page if you think it's badly out of date. I'm
intentionally leaving old pages there for historical reasons - if you
scanned down the wiki you'll have found that page in the "The Valley of
the Kings" section :-) (If you do create a new page, just put a note at
the start of the old page pointing to the new one.) Thing is, I've lost
a lot of references to lilo, grub-1, PATA drives, etc etc, and if
someone has an old system they'll want to find the old stuff.
Find a place in the current setup where you think it fits nicely,
rewrite it from scratch all up to date, and slot it in. Also note the
"editing guidelines" - they're pretty slack but I am trying to keep a
consistent editorial feel to the site - it just makes it a much
pleasanter place to read.
Cheers,
Wol
prev parent reply other threads:[~2018-02-07 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 19:10 Buffer I/O error... async page read Liwei
2018-02-06 13:55 ` Liwei
2018-02-07 6:27 ` Weedy
2018-02-07 7:02 ` Liwei
2018-02-07 14:54 ` Wols Lists [this message]
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=5A7B131C.1010102@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=weedy2887@gmail.com \
--cc=xieliwei@gmail.com \
/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.