Thanks! for suggesting Jason. More below.
On 06/19/2017 07:15 AM, Jason Detring wrote:
Hello list,
I'd like to request a new feature: make zlib compression level a tuneable.
The general use-case is a device where CPU cycles are "cheap enough",
but backing storage is expensive or difficult-to
I have subscribed successfully and am able to post successfully and
eventually view the post on spinics.net when it becomes available:
eg: http://www.spinics.net/lists/linux-btrfs/msg66605.html
However I do not know how to reply to messages, especially my own to
add more information, such as a cal
2017-06-02 1:57 GMT+03:00 Liu Bo :
> On Thu, Jun 01, 2017 at 11:26:26PM +0300, Ivan Sizov wrote:
>> 2017-06-01 20:35 GMT+03:00 Liu Bo :
>> > After I went through the output of leaf's content, most parts of the
>> > leaf is sane except the two corrupted items, it's still not clear to
>> > me what ca
Further to the above message reporting problems, I have been able to
capture a call trace under the main system rather than live media.
Note this occurred in rsync from btrfs to a separate drive running xfs
on a local filesystem (both sata drives). So I presume that btrfs is
only reading the drive
You should reply both to linux-btrfs@vger.kernel.org and the person
whom you talk to.
2017-06-19 11:37 GMT+03:00 Jesse :
> I have subscribed successfully and am able to post successfully and
> eventually view the post on spinics.net when it becomes available:
> eg: http://www.spinics.net/lists/lin
Ok thanks Ivan.
So I guess that means when I initiate a post, I also need to send it
to myself as well as the mail list.
Does it make any difference where I put respective addresses, eg: TO: CC: BCC:
Regards
Jesse
On 19 June 2017 at 17:20, Ivan Sizov wrote:
> You should reply both to linux-btr
2017-06-19 12:32 GMT+03:00 Jesse :
> So I guess that means when I initiate a post, I also need to send it
> to myself as well as the mail list.
You need to do it in the reply only, not in the initial post.
> Does it make any difference where I put respective addresses, eg: TO: CC: BCC:
You need to
Thanks Ivan.
What about when initiating a post, do I do the same eg:
TO: myself
CC: mailing list
or do I
TO: mailing list
CC: myself
TIA
On 19 June 2017 at 17:48, Ivan Sizov wrote:
> 2017-06-19 12:32 GMT+03:00 Jesse :
>> So I guess that means when I initiate a post, I also need to send it
>> to
2017-06-19 13:03 GMT+03:00 Jesse :
> Thanks Ivan.
> What about when initiating a post, do I do the same eg:
> TO: myself
> CC: mailing list
>
> or do I
> TO: mailing list
> CC: myself
When initiating a post you should to specify "TO: mailing list" only,
without any other addresses. At least I used
2017-06-19 13:03 GMT+03:00 Jesse :
> Thanks Ivan.
> What about when initiating a post, do I do the same eg:
> TO: myself
> CC: mailing list
>
> or do I
> TO: mailing list
> CC: myself
If your mail client doesn't have "sent" folder, you can, of course,
follow one of these examples. But I didn't face
2017-06-19 13:15 GMT+03:00 Jesse :
> Thanks again. So am I to understand that you go into your 'sent'
> folder, find a mail to the mail list (that is not CC to yourself),
> then you reply to this and add the mail list when you need to update
> your own post that no-one has yet replied to?
Yes, exac
On Sunday, October 2, 2016 6:54:09 PM IST Chandan Rajendra wrote:
> Btrfs assumes block size to be the same as the machine's page
> size. This would mean that a Btrfs instance created on a 4k page size
> machine (e.g. x86) will not be mountable on machines with larger page
> sizes (e.g. PPC64/AARCH
I just noticed a series of seemingly btrfs related call traces that
for the first time, did not lock up the system.
I have uploaded dmesg to https://paste.ee/p/An8Qy
Anyone able to help advise on these?
Thanks
Jesse
On 19 June 2017 at 17:19, Jesse wrote:
> Further to the above message report
This function is supposed to return blk_status_t error codes now but
there was a stray -ENOMEM left behind.
Fixes: 4e4cbee93d56 ("block: switch bios to blk_status_t")
Signed-off-by: Dan Carpenter
diff --git a/fs/btrfs/compression.c b/fs/btrfs/compression.c
index e536e98fe351..2c0b7b57fcd5 100644
On 16-06-17 03:43, Qu Wenruo wrote:
> Since incompat feature NO_HOLES still allow us to have explicit hole
> file extent, current check is too restrict and will cause false alert
> like:
>
> root 5 EXTENT_DATA[257, 0] shouldn't be hole
>
> Fix it by removing the restrict hole file extent check.
>
>
On Thu 01-06-17 13:34:34, Jan Kara wrote:
> On Thu 01-06-17 11:26:08, David Howells wrote:
> > Jan Kara wrote:
> >
> > > The callback doesn't ever get called. Remove it.
> >
> > Hmmm... I should perhaps be calling this. I'm not sure why I never did.
> >
> > At the moment, it doesn't strictly
On Thu, Jun 15, 2017 at 9:13 AM, Qu Wenruo wrote:
>
>
> At 06/14/2017 09:39 PM, Henk Slager wrote:
>>
>> On Tue, Jun 13, 2017 at 12:47 PM, Henk Slager wrote:
>>>
>>> On Tue, Jun 13, 2017 at 7:24 AM, Kai Krakow wrote:
Am Mon, 12 Jun 2017 11:00:31 +0200
schrieb Henk Slager :
>>
>> I think I leave it as is for the time being, unless there is some news
>> how to fix things with low risk (or maybe via a temp overlay snapshot
>> with DM). But the lowmem check took 2 days, that's not really fun.
>> The goal for the 8TB fs is to have an up to 7 year snapshot history at
>> somet
On Mon, Jun 19, 2017 at 12:48:54PM +0300, Ivan Sizov wrote:
> 2017-06-19 12:32 GMT+03:00 Jesse :
> > So I guess that means when I initiate a post, I also need to send it
> > to myself as well as the mail list.
> You need to do it in the reply only, not in the initial post.
>
> > Does it make any d
On Fri, 2017-06-16 at 15:34 -0400, Jeff Layton wrote:
> v7:
> ===
> This is the seventh posting of the patchset to revamp the way writeback
> errors are tracked and reported.
>
> The main difference from the v6 posting is the removal of the
> FS_WB_ERRSEQ flag. That requires a few other incrementa
On Fri, Jun 16, 2017 at 02:39:18PM +0300, Nikolay Borisov wrote:
> Hello,
>
> Here is a small series which fixes an issue that got reported internally to
> Suse and which affects devices whose size is not multiple of sectorsize. More
> information can be found in the changelog for patch 2
>
> T
On Sat, Jun 17, 2017 at 08:39:53AM -0400, Jeff Layton wrote:
> On Fri, 2017-06-16 at 15:34 -0400, Jeff Layton wrote:
> > Jan Kara's description for this patch is much better than mine, so I'm
> > quoting it verbatim here:
> >
> > DAX currently doesn't set errors in the mapping when cache flushing
Hi, for last several days i try work on entropy calculation that can
be usable in btrfs compression code (for detect bad compressible
data),
I've implemented:
- avg meaning (Problems with accuracy)
- shannon entropy
- shannon entropy with only integer logic (Accuracy compared to float
shannon +-0.
Hi Jeff,
On Mon, 19 Jun 2017 12:23:46 -0400 Jeff Layton wrote:
>
> If there are no major objections to this set, I'd like to have
> linux-next start picking it up to get some wider testing. What's the
> right vehicle for this, given that it touches stuff all over the tree?
>
> I can see 3 potent
Hello,
How are you doing? I have been sent to inform you that, We have an
inheritance of a deceased client with your surname. Contact Mr Andrew
Bailey Reply Email To: myinf...@gmail.com with your "Full Names" for
more info. Thanks for your understanding.
Reply ASAP thank you.
Melissa.
-
Thanks Мяу!
I will ensure I reply all :)
On 19 June 2017 at 23:38, Adam Borowski wrote:
> On Mon, Jun 19, 2017 at 12:48:54PM +0300, Ivan Sizov wrote:
>> 2017-06-19 12:32 GMT+03:00 Jesse :
>> > So I guess that means when I initiate a post, I also need to send it
>> > to myself as well as the mail
On 15.06.2017 20:10, David Sterba wrote:
> We can keep the state among the other fs_info flags, there's no reason
> why fs_frozen would need to be separate.
>
> Signed-off-by: David Sterba
Reviewed-by: Nikolay Borisov
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" i
On 15.06.2017 20:09, David Sterba wrote:
> The pattern when err is used for function exit and ret is used for
> return values of callees is not used here.
>
> Signed-off-by: David Sterba
Reviewed-by: Nikolay Borisov
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
28 matches
Mail list logo
