Christoph Anton Mitterer posted on Sat, 12 Dec 2015 23:15:38 +0100 as
excerpted:
> On Sat, 2015-11-28 at 06:49 +, Duncan wrote:
>> Christoph Anton Mitterer posted on Sat, 28 Nov 2015 04:57:05 +0100 as
>> excerpted:
>> > Still, specifically for snapshots that's a bit unhandy, as one
>> >
Hi all,
I am searching a project to start contribute to the btrfs-progs code
and I have became interested to get more information about the "add
API for tree search ioctl " project. The first information required is
if there is anyone working on it.
The other information is if this API will be
Chris Murphy posted on Sat, 12 Dec 2015 13:16:41 -0700 as excerpted:
> On Sat, Dec 12, 2015 at 3:34 AM, Ivan Sizov wrote:
>> 2015-12-11 21:24 GMT+03:00 Chris Murphy :
>>> I would not repair it if the risk of it getting worse is bad for your
>>> data.
Christoph Anton Mitterer posted on Sat, 12 Dec 2015 03:32:57 +0100 as
excerpted:
> [B]etter said I largely rewrote:
> https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Subvolumes
> which I think should rather be its own wiki article.
>
> One of the devs/experts... please double check it and
2015-12-11 21:24 GMT+03:00 Chris Murphy :
> I would not repair it if the risk of it getting worse is bad for your data.
>
> Note the wiki says this feature is not well tested and is reported to
> not work reliably.
>
I had a similar issue yesterday, although the fs is not a converted
one. It just started with this in dmesg:
BTRFS critical (device sdf1): corrupt leaf, slot offset bad:
block=77130973184,root=1, slot=150
I hope you can still mount RO, but I don't know a way to preserve the
btrfs CoW
On Wed, 2015-12-09 at 10:53 +, Duncan wrote:
> If you use the recipe (subvol create, cp with reflink) it suggests
> there,
> you'll end up with the reflinked copy in a subvol.
>
> You can then mount that subvol over top of the existing dir, and
> *new*
> file opens will access the new
On Sat, Dec 12, 2015 at 3:34 AM, Ivan Sizov wrote:
> 2015-12-11 21:24 GMT+03:00 Chris Murphy :
>> I would not repair it if the risk of it getting worse is bad for your data.
>>
>> Note the wiki says this feature is not well tested and is reported to
>>
On Thu, 2015-12-10 at 19:32 -0700, Chris Murphy wrote:
> That seems due for a revision because I do rw, ro, rw, rw, ro mounts
> in sequence and they stick fine. In fact they stick with the same
> subvolume.
>
> [root@f23m ]# mount /dev/sda7 /mnt/1 -o subvol=home
> [root@f23m ]# mount /dev/sda7
On Sat, 2015-12-12 at 13:16 -0700, Chris Murphy wrote:
> > What is the better way to get data? send/receive works only with RO
> > snapshots. Is there another way to preserve subvolumes and CoW
> > structure (a lot of files was copied between subvols using "cp
> > --reflink=always")? Or just
On Wed, Dec 09, 2015 at 10:19:41AM +, Duncan wrote:
> Alistair Grant posted on Wed, 09 Dec 2015 09:38:47 +1100 as excerpted:
>
> > On Tue, Dec 08, 2015 at 03:25:14PM +, Duncan wrote:
> > Thanks again Duncan for your assistance.
> >
> > I plugged the ext4 drive I planned to use for the
On Sat, 2015-11-28 at 06:49 +, Duncan wrote:
> Christoph Anton Mitterer posted on Sat, 28 Nov 2015 04:57:05 +0100 as
> excerpted:
> > Still, specifically for snapshots that's a bit unhandy, as one
> > typically
> > doesn't mount each of them... one rather mount e.g. the top level
> > subvol
>
12 matches
Mail list logo