Originally this test case was designed to work with 4K sectorsize.
Now enhance it to work with any sector sizes and makes the following
changes:
.out file not to contain any traces of sector size.
Use max_inline=0 mount option so that it meets the requisite of non inline
regular extent.
Don't log
On 16/09/18, Chris Murphy (li...@colorremedies.com) wrote:
> > So I did this:
> >
> > btrfs subvol snapshot /bkp /bkp/backup-subvol
> >
> > strangely while /bkp/backup has lots of files in it,
> > /bkp/backup-subvol/backup has none.
> >
> > # btrfs subvol list /bkp
> > ID 258 gen 313585 top
Hello all
Actually I'm not trying to get any help any more, I gave up BTRFS on
the desktop, but I'd like to share my efforts of trying to fix my
problems, in hope I can help some poor noob like me.
I decided to use BTRFS after reading the ArsTechnica article about the
next-gen filesystems, and
On Sun, Sep 16, 2018 at 7:58 AM, Adrian Bastholm wrote:
> Hello all
> Actually I'm not trying to get any help any more, I gave up BTRFS on
> the desktop, but I'd like to share my efforts of trying to fix my
> problems, in hope I can help some poor noob like me.
There's almost no useful
Hi
We have a backup machine that has been happily running its backup
partitions on btrfs (on top of a luks encrypted disks) for a few years.
Our backup partition is on /bkp which is a top level subvolume.
Data, RAID1: total=2.52TiB, used=1.36TiB
There are no other subvolumes.
We have /bkp
On 2018/9/16 下午9:58, Adrian Bastholm wrote:
> Hello all
> Actually I'm not trying to get any help any more, I gave up BTRFS on
> the desktop, but I'd like to share my efforts of trying to fix my
> problems, in hope I can help some poor noob like me.
>
> I decided to use BTRFS after reading the
On Sun, Sep 16, 2018 at 5:14 AM, Rory Campbell-Lange
wrote:
> Hi
>
> We have a backup machine that has been happily running its backup
> partitions on btrfs (on top of a luks encrypted disks) for a few years.
>
> Our backup partition is on /bkp which is a top level subvolume.
> Data, RAID1:
On 16/09/18, Hans van Kranenburg (hans.van.kranenb...@mendix.com) wrote:
> On 09/16/2018 02:37 PM, Hans van Kranenburg wrote:
> > On 09/16/2018 01:14 PM, Rory Campbell-Lange wrote:
...
> >> We have /bkp with /bkp/backup in it. We would like to mount /bkp/backup
> >> at /bkp instead. Note that
On 09/16/2018 01:14 PM, Rory Campbell-Lange wrote:
> Hi
>
> We have a backup machine that has been happily running its backup
> partitions on btrfs (on top of a luks encrypted disks) for a few years.
>
> Our backup partition is on /bkp which is a top level subvolume.
> Data, RAID1:
Thanks very much for the reply, Hans. I'm just responding to your note
about mout options here.
On 16/09/18, Hans van Kranenburg (hans.van.kranenb...@mendix.com) wrote:
> > The machine is btrfs-progs v4.7.3 Linux 4.9.0-8-amd64 on Debian. The
> > coreutils version is 8.26-3.
>
> Another note:
> So I did this:
>
> btrfs subvol snapshot /bkp /bkp/backup-subvol
>
> strangely while /bkp/backup has lots of files in it,
> /bkp/backup-subvol/backup has none.
>
> # btrfs subvol list /bkp
> ID 258 gen 313585 top level 5 path backup
> ID 4782 gen 313590 top level 5 path backup-subvol
OK so
On 09/16/2018 02:37 PM, Hans van Kranenburg wrote:
> On 09/16/2018 01:14 PM, Rory Campbell-Lange wrote:
>> Hi
>>
>> We have a backup machine that has been happily running its backup
>> partitions on btrfs (on top of a luks encrypted disks) for a few years.
>>
>> Our backup partition is on /bkp
...
And also raid56 is still considered experimental, and has various
problems if the hardware lies (like if some writes happen out of order
or faster on some devices than others,and it's much harder to repair
because the repair tools aren't raid56 feature complete).
On Sun, Sep 16, 2018 at 2:11 PM, Adrian Bastholm wrote:
> Thanks for answering Qu.
>
>> At this timing, your fs is already corrupted.
>> I'm not sure about the reason, it can be a failed CoW combined with
>> powerloss, or corrupted free space cache, or some old kernel bugs.
>>
>> Anyway, the
On 9/14/2018 10:34 PM, David Sterba wrote:
On Wed, Sep 12, 2018 at 03:39:03PM +0800, Su Yanjun wrote:
Modify the file name length limit to meet the Linux naming convention.
In addition, the file name length is always bigger than 0, no need to
compare with 0 again.
Issue: #145
Signed-off-by:
On Sun, Sep 16, 2018 at 12:40 PM, Rory Campbell-Lange
wrote:
> Thanks very much for spotting my error, Chris.
>
> # mount | grep bkp
> /dev/mapper/cdisk2 on /bkp type btrfs
> (rw,noatime,compress=lzo,space_cache,subvolid=5,subvol=/)
>
> # btrfs subvol list /bkp
> ID 258 gen
16 matches
Mail list logo