On 7/6/2017 2:26 AM, Duncan wrote:
> Daniel Brady posted on Wed, 05 Jul 2017 22:10:35 -0600 as excerpted:
>
>> My system suddenly decided it did not want to mount my BTRFS setup. I
>> recently rebooted the computer. When it came back, the file system was
>> in read only mode. I gave it another boot
From: Omar Sandoval
If a lot of metadata is reserved for outstanding delayed allocations, we
rely on shrink_delalloc() to reclaim metadata space in order to fulfill
reservation tickets. However, shrink_delalloc() has a shortcut where if
it determines that space can be overcommitted, it will stop
On Wed, 5 Jul 2017 22:10:35 -0600
Daniel Brady wrote:
> parent transid verify failed
Typically in Btrfs terms this means "you're screwed", fsck will not fix it, and
nobody will know how to fix or what is the cause either. Time to restore from
backups! Or look into "btrfs restore" if you don't ha
On Thu, Jul 06, 2017 at 04:59:39PM -0700, Marc MERLIN wrote:
> On Thu, Jul 06, 2017 at 04:44:51PM -0700, Omar Sandoval wrote:
> > In the bug report, you commented that CURRENT contained MANIFEST-010814,
> > is that indeed the case or was it actually something newer? If it was
> > the newer one, the
On Thu, Jul 06, 2017 at 10:37:18PM -0700, Marc MERLIN wrote:
> I'm still trying to fix my filesystem.
> It seems to work well enough since the damage is apparently localized, but
> I'd really want check --repair to actually bring it back to a working
> state, but now it's crashing
>
> This is btrf
I'm still trying to fix my filesystem.
It seems to work well enough since the damage is apparently localized, but
I'd really want check --repair to actually bring it back to a working
state, but now it's crashing
This is btrfs tools from git from a few days ago
Failed to find [4068943577088, 168,
On Fri, Jun 23, 2017 at 04:25:43PM +0800, Eryu Guan wrote:
> On Wed, Jun 21, 2017 at 10:50:35AM +0300, Nikolay Borisov wrote:
> > When changing the size of disks/filesystem we should always be
> > rounding down to a multiple of sectorsize
> >
> > Signed-off-by: Nikolay Borisov
>
> Thanks for the
On Thu, Jul 06, 2017 at 04:44:51PM -0700, Omar Sandoval wrote:
> In the bug report, you commented that CURRENT contained MANIFEST-010814,
> is that indeed the case or was it actually something newer? If it was
> the newer one, then it's still tricky how we'd end up that way but not
> as outlandish.
On Thu, Jul 06, 2017 at 04:31:52PM -0700, Marc MERLIN wrote:
> On Thu, Jul 06, 2017 at 04:01:41PM -0700, Omar Sandoval wrote:
> > What doesn't add up about your bug report is that your CURRENT points to
> > a MANIFEST-010814 way behind all of the other files in that directory,
> > which are numbere
On Thu, Jul 06, 2017 at 04:01:41PM -0700, Omar Sandoval wrote:
> What doesn't add up about your bug report is that your CURRENT points to
> a MANIFEST-010814 way behind all of the other files in that directory,
> which are numbered 022745+. If there were a bug here, I'd expect the
> stale MANIFEST
On Thu, Jul 06, 2017 at 02:24:22PM -0700, Marc MERLIN wrote:
> On Thu, Jul 06, 2017 at 02:13:20PM -0700, Omar Sandoval wrote:
> > On Thu, Jul 06, 2017 at 08:00:46AM -0700, Marc MERLIN wrote:
> > > I don't know who else uses google-chrome here, but for me, for as long as
> > > I've used btrfs (3+ ye
On Thu, Jul 06, 2017 at 02:13:20PM -0700, Omar Sandoval wrote:
> On Thu, Jul 06, 2017 at 08:00:46AM -0700, Marc MERLIN wrote:
> > I don't know who else uses google-chrome here, but for me, for as long as
> > I've used btrfs (3+ years now), I've had no end of troubles recovering from
> > a linux cra
On Thu, Jul 06, 2017 at 08:00:46AM -0700, Marc MERLIN wrote:
> I don't know who else uses google-chrome here, but for me, for as long as
> I've used btrfs (3+ years now), I've had no end of troubles recovering from
> a linux crash, and google-chrome has had problems recovering my tabs and
> usually
On Thu, Jun 29, 2017 at 12:41:07PM -0700, Nick Terrell wrote:
> Add zstd compression and decompression support to BtrFS. zstd at its
> fastest level compresses almost as well as zlib, while offering much
> faster compression and decompression, approaching lzo speeds.
Got a reproducible crash on am
I don't know who else uses google-chrome here, but for me, for as long as
I've used btrfs (3+ years now), I've had no end of troubles recovering from
a linux crash, and google-chrome has had problems recovering my tabs and
usually cmoplains about plenty of problems, some are corruption looking.
Th
On 2017-07-06 08:09, Lionel Bouton wrote:
Le 06/07/2017 à 13:59, Austin S. Hemmelgarn a écrit :
On 2017-07-05 20:25, Nick Terrell wrote:
On 7/5/17, 12:57 PM, "Austin S. Hemmelgarn"
wrote:
It's the slower compression speed that has me arguing for the
possibility of configurable levels on zlib.
> -Original Message-
> From: Austin S. Hemmelgarn [mailto:ahferro...@gmail.com]
> Sent: Thursday, 6 July 2017 9:52 PM
> To: Paul Jones ; linux-btrfs@vger.kernel.org
> Subject: Re: Btrfs Compression
>
> On 2017-07-05 23:19, Paul Jones wrote:
> > While reading the thread about adding zstd co
Le 06/07/2017 à 13:59, Austin S. Hemmelgarn a écrit :
> On 2017-07-05 20:25, Nick Terrell wrote:
>> On 7/5/17, 12:57 PM, "Austin S. Hemmelgarn"
>> wrote:
>>> It's the slower compression speed that has me arguing for the
>>> possibility of configurable levels on zlib. 11MB/s is painfully slow
>>>
Le 06/07/2017 à 13:51, Austin S. Hemmelgarn a écrit :
>
> Additionally, when you're referring to extent size, I assume you mean
> the huge number of 128k extents that the FIEMAP ioctl (and at least
> older versions of `filefrag`) shows for compressed files? If that's
> the case, then it's importan
On 2017-07-05 20:25, Nick Terrell wrote:
On 7/5/17, 12:57 PM, "Austin S. Hemmelgarn" wrote:
It's the slower compression speed that has me arguing for the
possibility of configurable levels on zlib. 11MB/s is painfully slow
considering that most decent HDD's these days can get almost 5-10x that
On 2017-07-05 23:19, Paul Jones wrote:
While reading the thread about adding zstd compression, it occurred
to me that there is potentially another thing affecting performance -
Compressed extent size. (correct my terminology if it's incorrect). I
have two near identical RAID1 filesystems (used fo
Daniel Brady posted on Wed, 05 Jul 2017 22:10:35 -0600 as excerpted:
> My system suddenly decided it did not want to mount my BTRFS setup. I
> recently rebooted the computer. When it came back, the file system was
> in read only mode. I gave it another boot, but now it does not want to
> mount at
22 matches
Mail list logo
