[sheepdog-users] snapshot & sheepfs

[Marcin Mirosław]

W dniu 26.05.2015 o 05:16, Liu Yuan pisze:

Hi Liu!

> On Tue, May 26, 2015 at 10:04:57AM +0800, Liu Yuan wrote:
>> On Mon, May 25, 2015 at 05:13:45PM +0200, Marcin Mirosław wrote:
>>> Hi again!
>>> I've got problem when I'm using sheepfs to access vdi and I create
>>> snapshot. Please look:
>>> # sheepfs /mnt/sheep
>>> # echo testowy > /mnt/sheep/vdi/mount
>>> # fsck.ext4 -f /mnt/sheep/volume/testowy
>>> e2fsck 1.42.13 (17-May-2015)
>>> Przebieg 1: Sprawdzanie i-węzłów, bloków i rozmiarów
>>> Przebieg 2: Sprawdzanie struktury katalogów
>>> Przebieg 3: Sprawdzanie łączności katalogów
>>> Przebieg 4: Sprawdzanie liczników odwołań
>>> Przebieg 5: Sprawdzanie sumarycznych informacji o grupach
>>> /mnt/sheep/volume/testowy: 66149/655360 plików (0.1% nieciągłych),
>>> 1053139/2621440 bloków
>>>
>>> Everything is ok.
>>> Now:
>>> # dog vdi snapshot -s pierwszysnap testowy
>>> # LC_ALL=en_US.utf-8 fsck.ext4 -f /mnt/sheep/volume/testowy
>>> e2fsck 1.42.13 (17-May-2015)
>>> Error writing block 1081344 (Attempt to write block to filesystem
>>> resulted in short write).  Ignore error<y>? cancelled!
>>>
>>> Umounting and mounting sheepfs doesn't change anything. Is sheepfs using
>>> vdi or it mounts snapshot?
>>> Sheepdog HEAD.
>>> Marcin
>>
>> sheepfs doesn't reload inode after snapshoting yet. This is a bug of sheepfs
>> that need to be fixed.
>>
> 
> As a workaround, you may try offline snapshot:
> 
> 1 umount vdi
> 2 dog vdi snapshot vdi
> 3 mount vdi again (this will reload the right vdi's meta data)

It doesn't help, sheepfs can't handle vdi with snapshot even with this
trick.
Thanks for answer.
Marcin