Re: Incompat features: raid56 ... when creating a RAID6?

[Duncan <1i5t5.duncan@cox.net>]

Andreas Grosse posted on Wed, 16 Mar 2016 10:12:47 +0100 as excerpted:

> Am Mittwoch, 16. MÀrz 2016, 08:52:52 CET schrieb Anand Jain:
>>   Yes looks like. As it was there when I read your posting.
>> 
>> 
>> >>> AndiN‹§²Êìrž›yúÚšØb²X¬¶Ç§vØ^–)Þº
{.nÇ+‰·¥Š{±nÚß²)í ÊÚw*\x1fjg¬±š\x1e¶‰šŜŠÝ¢j/
ê
>> >>> Àz
>> >>> ¹Þ–Šà2ŠÞ™šÚ­Ú&¢)ßÂ
¡Â«a¶Ú\x7fßÞ\x1e®G«éh®\x0fÊj:+v‰šŠwÚ†Ù¥
> 
> I'll have a look at this. I have no idea where this came from. But it
> seems this stuff is invisible on the list archives on the web on my
> initial message...
> 
> N‹§²æìrž›yúèšØb²X¬¶Ç§vØ^–)Þº{.nÇ+‰·¥Š{±nÚß²)í…æèw*\x1fjg¬
±š\x1e¶‰šŽŠÝ¢j/êäz¹Þ–Šà2ŠÞ™šè­Ú&¢)ß¡«a¶Ú\x7fþø\x1e®G«éh®\x0fæj:
+v‰šŠwè†Ù¥


FWIW, your posting as it appeared on gmane's news (nntp, which I use for 
this list) and web archives was truncated.  Hugo evidently got a better 
copy than gmane did, as he quoted text that wasn't there for me.

Here's (one of) the gmane web link(s) to your post on the web archive:

http://permalink.gmane.org/gmane.comp.file-systems.btrfs/54108

As you can see, it's truncated there, tho the web interface doesn't let 
you see the raw message.

The nntp/news archive does better at letting you at the raw message.  I 
use pan as my nntp client, and fetched the raw message file itself from 
cache after getting the messageID from the pan GUI.  Unfortunately, not a 
lot of web or mail clients know what to do with links like...

nntp://news.gmane.org/gmane.comp.file-systems.btrfs

... and I don't remember how to add the specific article to the link.  So 
you may have trouble getting the article from news.

Tho AFAIK lynx, the text-mode browser, can handle news.  You might try 
that.


I could send you personally a copy of the message file, however, if you 
like.  Selected headers say:

User-Agent: KMail/ (Linux/4.5.0-gentoo; KDE/5.20.0; x86_64; ; )
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64


With the base64 encoding, of course the raw message body is just a big 
block of ASCII chars encoding the base64 ... notably, with the list 
footer/signature appended below in plain 7-bit ASCII.  I wonder if some 
clients (including pan, it would appear, tho gmane's web interface 
displayed the same body I saw in pan) can't handle the mix of base64 
encoding and plain 7-bit ASCII?, in a message the headers clearly state 
as base64 encoded?  Certainly, the listserv shouldn't just add a plain-
text blob of text to a message body that is base64 encoded like that, 
instead making it multi-part and putting the sig in a 7-bit ascii or 
whatever encoding, if need be, or decoding the base64, appending the text 
blob, and recoding, but regardless, if that's all the "corruption" is, 
clients should handle it better than trucating and/or corrupting.

I didn't try to manually decode the block of base64 either using uudeview 
or the like or fully manually, to see if it stopped at the same spot, or 
included the corruption, or something else, but I do have the full raw 
message file as downloaded via gmane using pan, and can mail it to you 
privately if you'd like.  Tho if you're familiar at all with news and 
have a client to use on news.gmane.org, or simply have lynx around and 
can follow the link above in it, you can find and grab the news article 
for yourself.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman