Hi,
please keep this on the list, if somebody else is following.
On Wed, Dec 26, 2012 at 10:38 PM, nafisa mandliwala
nafisa.mandliw...@gmail.com wrote:
hey :)
I've figured out how to correct the above errors.
I have a few doubts related to the code
1.btrfs_compare_trees :
this is
On Thu, Dec 27, 2012 at 9:18 AM, nafisa mandliwala
nafisa.mandliw...@gmail.com wrote:
Specifically what do the functions btrfs_item_ptr and btrfs_inode_generation
do?
You need to spend some time on btrfs basics, specifically look at how
btrfs leaf looks like. How items and their data are layed
On 12/28/2012 08:03 PM, David Sterba wrote:
On Fri, Dec 28, 2012 at 11:42:40AM +0800, Jeff Liu wrote:
+static int btrfs_ioctl_set_fslabel(struct file *file, void __user *arg)
+{
+struct btrfs_root *root = BTRFS_I(fdentry(file)-d_inode)-root;
+struct btrfs_super_block *super_block =
Small correction,I was just hit by this:
# The tuple (inode_number, inode generation) is unique within a
particular btrfs subvolume. Inode numbers can be reused via
inode_cache mount option if it is set, however, same inode number
(after deletion of previous one) will have another inode
Hi Chris! Hi Alexander!
I'm working on the kernel side of a feature request we have from the snapper
developers. Snapper can be used (in conjunction) with btrfs on openSUSE to
roll back system changes made via YaST and zypper.
If you want to know more, you can see the following page:
