On Mon, Feb 09, 2015 at 07:56:24AM +0800, Anand Jain wrote:
> This adds an enhancement to show the seed fsid and devices.
>
> The way sprouting handles fs_devices:
> clone seed fs_devices and add to the fs_uuids
> mem copy seed fs_devices and assign to fs_devices->seed (move dev_list)
> evacuate seed fs_devices contents to hold sprout fs devices contents
>
> So to be inline with this fs_devices changes during seeding,
> represent seed fsid under the sprout fsid, this is achieved
> by using the kobject_move()
>
> eg: showing two levels of seeding.
That's new to me, how does nested seeding work?
> find /sys/fs/btrfs/ -type d -name devices -exec ls {} \; -print
>
> sde
> /sys/fs/btrfs/8c2772d4-6951-43c3-89b6-3ab3c70a13f8/f7ef2904-ce89-4421-bfb0-49fd999e9a0b/devices
> sdd
> /sys/fs/btrfs/8c2772d4-6951-43c3-89b6-3ab3c70a13f8/f7ef2904-ce89-4421-bfb0-49fd999e9a0b/53ac3265-0c34-4afd-9453-cc0d1a07be64/devices
The plain uuid is IMHO not the best naming convention, although it's
acceptable in the global list in /sys/fs/btrfs/* I'd rather avoid it if
it's mixed with other files.
Would it be enough to print all relevant seeding information into a
single file? If the "UUID" directoreis do not contain anything else,
that would be IMHO best.
Do the seeding fsids exist on their own in /sys/sf/btrfs? I haven't
tested the patchset so I'd probably find that out myself.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
