You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using f2fs on one of my pi's, and each time rpi-clone runs, it reports:
Editing /mnt/clone/etc/fstab PARTUUID to use ea0b56b4
e2label: Bad magic number in super-block while trying to open /dev/sda2
Which makes sense, since you can't add an extX label to an f2fs filesystem. I've tested the backups, they work fine, so this is a cosmetic error at worst.
The text was updated successfully, but these errors were encountered:
I should probably add - the script is invoked nightly as:
/usr/local/sbin/rpi-clone -u -v sda
So I'm not declaring that a label should be written. Likewise, the logic in the script appears to suggest that it should not be trying to write a label on a non ext filesystem, which is why this appears to be a bug. However, I'm not a coder, so my interpretation of what the script is doing may be faulty.
I'm using f2fs on one of my pi's, and each time rpi-clone runs, it reports:
Editing /mnt/clone/etc/fstab PARTUUID to use ea0b56b4
e2label: Bad magic number in super-block while trying to open /dev/sda2
Which makes sense, since you can't add an extX label to an f2fs filesystem. I've tested the backups, they work fine, so this is a cosmetic error at worst.
The text was updated successfully, but these errors were encountered: