Hi Filipe,
There is another case for 2nd scenario where is_ancestor() can't be used.
Parent snapshot:
| a/ (ino 261)
| c (ino 267)
| d/ (ino 259)
| ance/ (ino 266)
| waiting_dir/ (ino 262)
| pre/ (ino 264)
| ance/ (ino 265)
Send snapshot:
| a/ (ino 261)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/2015 04:25 PM, Anand Jain wrote:
>> typically ready cli is to check disk pool status in an unmounted
>> state.
On my desktop with btrfs RAID0 on two partitions, the exit code of
ready is always 1. On my laptop with btrfs RAID0 on two LUKS/dm
> 2015-06-04 16:42 GMT+02:00 Richard Michael :
>> Hi Johan,
[snip]
>> Concerning the backup of subvolumes, Snazzer is frequently mentioned. (I
>> have not used it myself.)
>>
>> https://github.com/csirac2/snazzer
Just a heads-up: those frequent mentions are entirely down to me
trying to gain some
On 06/05/2015 01:57 AM, Roger Binns wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is on current Ubuntu 15.04. What is device ready unhappy with?
Note that the root filesystem and /home (both subvolumes of this) are
mounted and working perfectly, and even where the commands are run
Neil Horman pointed out a problem where if he did something like this
receive A
snap A B
change B
send -p A B
and then on another box do
recieve A
receive B
the receive B would fail because we use the UUID of A for the clone sources for
B. This makes sense most of the time because normally you
On Thu, Jun 4, 2015 at 2:50 PM, Filipe David Manana wrote:
> On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
>> Base on [PATCH] Btrfs: incremental send, check if orphanized dir inode needs
>> delayed rename
>>
>> Example1:
>> There's one case where we can't issue a rename operation for a direc
Hi folks,
Well, we made it! As of yesterday, the File & Storage systems microconf has
been approved for Plumbers! If you're interested in attending, I highly
recommend that you register[0] immediately, as the earlybird deadline is
tomorrow, June 5th.
We have a solid list of discussion ideas on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is on current Ubuntu 15.04. What is device ready unhappy with?
Note that the root filesystem and /home (both subvolumes of this) are
mounted and working perfectly, and even where the commands are run from.
$ sudo btrfs fi show /dev/sda1
Label: '
On Thu, Jun 4, 2015 at 1:09 PM, Zhaolei wrote:
> From: Zhao Lei
>
> lockdep report following warning in test:
> [25176.843958] =
> [25176.844519] [ INFO: inconsistent lock state ]
> [25176.845047] 4.1.0-rc3 #22 Tainted: GW
> [25176.845591] -
On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
> There's one case where we can't rmdir issue.
"There's one case where we attempt to rmdir a directory prematurely."
>
> Example:
>
> Parent snapshot:
> | a/ (ino 279)
> | c (ino 282)
> | del/ (ino 281)
> | tmp/ (ino 280)
>
Yes, ReadyNAS btrfs is a long way away from 3.0 btrfs. And RN202/204
currently ship with a 3.12 kernel, and will be updated further soon.
There are also firmware versions currently available in beta for all
other hardware platforms using a much newer kernel, if you'd rather.
But anyway, here's a d
On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
> There's one case where we not clear orphan_dir_info issue.
You mean where we leak a orphan_dir_info structure.
>
> Example:
>
> Parent snapshot:
> | a/ (ino 279)
> | c (ino 282)
> | del/ (ino 281)
> | tmp/ (ino 280)
> |---
On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
> There's one case where we can't issue a utimes operation for a directory.
> When 263 will delete, waiting 261 and set 261 rmdir_ino, but 262 earlier
> processed and update uime between two parent directory.
> So fix this by not update non exist u
On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
> Base on [PATCH] Btrfs: incremental send, don't delay directory renames
> unnecessarily
>
> There's one case where we can't issue a rename operation for a directory
Should be "There's one more case where..." - we already have at least
a handful
Hey Martin,
On 04/06/2015 15:55:49, Martin Steigerwald wrote:
BTRFS and Kernel 3.0?
Unless its has a newer BTRFS version or at least critical fixed
backported, I would run away from it.
Free space management in Kernel 3.0 still had issues that even with 2
GiB free the filesystem could report i
On Wed, Jun 03 2015 at 9:42P -0400,
Christoph Hellwig wrote:
> Currently we have two different ways to signal an I/O error on a BIO:
>
> (1) by clearing the BIO_UPTODATE flag
> (2) by returning a Linux errno value to the bi_end_io callback
>
> The first one has the drawback of only communica
Hi Johan,
No, AFAIK, " send ... | .. receive " will not include subvolumes.
This was discussed in various threads on-list in late April/early May.
I suggest perusing these:
http://thread.gmane.org/gmane.comp.file-systems.btrfs/44459
http://thread.gmane.org/gmane.comp.file-systems.btrfs/44890
htt
Thank you! My fault.
2015-06-04 16:42 GMT+02:00 Richard Michael :
> Hi Johan,
>
> This was discussed in various threads on-list in late April/early May. I
> suggest perusing these:
>
> http://thread.gmane.org/gmane.comp.file-systems.btrfs/44459
> http://thread.gmane.org/gmane.comp.file-systems.bt
Hello,
I am wondering, what is the fastest und most secure way to copy a
complete btrfs-volume including the subvolume-structure to another
volume?
Just btrfs send/receive like this?
> btrfs send /vol1|btrfs receive vol2
Thanks in advance
Johan
--
To unsubscribe from this list: send the line "unsu
Am Donnerstag, 4. Juni 2015, 14:54:48 schrieb Maximilian Eschenbacher:
> Greetings,
>
> I am wondering about the stability of btrfs in this kernel version since
> Negear ist selling those ReadyNAS with a buttload of features including
> btrfs and linux kernel 3.0.
>
> Is this a system one can use
On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
> Base on [PATCH] Btrfs: incremental send, check if orphanized dir inode needs
> delayed rename
>
> Example1:
> There's one case where we can't issue a rename operation for a directory
> immediately when we process it.
>
> Parent snapshot:
> |
On Thu, Jun 4, 2015 at 12:18 PM, Robbie Ko wrote:
> Patch for fix btrfs send receive. These patches base on v4.1-rc6-49-g8a7deb3
> plus following patches.
> [PATCH] Btrfs: incremental send, don't delay directory renames unnecessarily
> [PATCH] Btrfs: incremental send, check if orphanized dir inode
Greetings,
I am wondering about the stability of btrfs in this kernel version since
Negear ist selling those ReadyNAS with a buttload of features including
btrfs and linux kernel 3.0.
Is this a system one can use to keep backup? Do you have any suggestions
on what operations may be cause problem
From: Zhao Lei
lockdep report following warning in test:
[25176.843958] =
[25176.844519] [ INFO: inconsistent lock state ]
[25176.845047] 4.1.0-rc3 #22 Tainted: GW
[25176.845591] -
[25176.846153] inconsistent {SOFTIRQ-ON
There's one case where we can't issue a utimes operation for a directory.
When 263 will delete, waiting 261 and set 261 rmdir_ino, but 262 earlier
processed and update uime between two parent directory.
So fix this by not update non exist utimes for this case.
Example:
Parent snapshot:
| a/ (
Base on [PATCH] Btrfs: incremental send, don't delay directory renames
unnecessarily
There's one case where we can't issue a rename operation for a directory
as soon as we process it. We move a directory from ancestor to descendant,
if not wait_parent_move or wait_for_dest_dir_move so that happen
There's one case where we not clear orphan_dir_info issue.
Example:
Parent snapshot:
| a/ (ino 279)
| c (ino 282)
| del/ (ino 281)
| tmp/ (ino 280)
| long/ (ino 283)
| longlong/ (ino 284)
Send snapshot:
| a/ (ino 279)
| long (ino 283)
| longlong (i
Patch for fix btrfs send receive. These patches base on v4.1-rc6-49-g8a7deb3
plus following patches.
[PATCH] Btrfs: incremental send, don't delay directory renames unnecessarily
[PATCH] Btrfs: incremental send, check if orphanized dir inode needs delayed
rename
Thanks.
Robbie Ko (5):
Btrfs: in
There's one case where we can't rmdir issue.
Example:
Parent snapshot:
| a/ (ino 279)
| c (ino 282)
| del/ (ino 281)
| tmp/ (ino 280)
| long/ (ino 283)
Send snapshot:
| a/ (ino 279)
| long (ino 283)
| c/ (ino 282)
| tmp/ (ino 280)
Here we process 28
Base on [PATCH] Btrfs: incremental send, check if orphanized dir inode needs
delayed rename
Example1:
There's one case where we can't issue a rename operation for a directory
immediately when we process it.
Parent snapshot:
| d/ (ino 257)
| p1 (ino 258)
| p1/ (ino 259)
Send snaps
On Wed, 03 Jun 2015 10:47:52 -0400, jeffm wrote:
> This patch iterates over the unused chunk space and discards any regions
> that are unallocated, regardless of whether they were ever used. This is
> a change for btrfs but is consistent with other file systems.
> ..
[snip]
This just gave me:
f
> "Christoph" == Christoph Hellwig writes:
Christoph> The first one has the drawback of only communicating a single
Christoph> possible error (-EIO), and the second one has the drawback of
Christoph> not beeing persistent when bios are queued up, and are not
Christoph> passed along from child
Hi Chris,
After our quick chat, I gave it a shot on 3.19.6, and things are better
than last time I tried.
legolas:/var/local/nobck/VirtualBox VMs# lsattr Win7/
---C Win7/Logs
---C Win7/Snapshots
---C Win7/Win7.vdi
---C Win7/Win7.png
---C
33 matches
Mail list logo
