Can't create snapshots anymore after successful disk expansions -> "Failed to create snapshot"

Hi all,

I recently expanded our Raid 6 setup from 4x3TB to 4x10TB which worked as expected. Snapshots were pruned before due to full disks - now after the expansions I was surprised to see that snapshots still got 0% of the overall disk volume even it is enabled to do a hourly snapshot. Creating a snapshot manually resulted into an "Failed to create snapshot" error message.

status.log

[18/02/12 12:37:13 CET] warning:snapshot:LOGMSG_SNAPSHOT_CREATE_WARN Failed to create snapshot initial for share or LUN 'eguoffice'.

system.log

Feb 12 12:37:13 io snapperd[3394]: THROW: stat on info directory failed
Feb 12 12:37:13 io snapperd[3394]: reading failed
Feb 12 12:37:13 io snapperd[3394]: THROW: stat on info directory failed
Feb 12 12:37:13 io snapperd[3394]: CAUGHT: stat on info directory failed
Feb 12 12:37:13 io msmtpq[8822]: mail for [ -C /etc/msmtprc [email protected] --timeout=60 ] : send was successful
Feb 12 12:37:45 io snapperd[3394]: THROW: stat on info directory failed
Feb 12 12:37:45 io snapperd[3394]: reading failed
Feb 12 12:37:45 io snapperd[3394]: THROW: stat on info directory failed
Feb 12 12:37:45 io snapperd[3394]: reading failed
Feb 12 12:37:45 io snapperd[3394]: THROW: stat on info directory failed
Feb 12 12:37:45 io snapperd[3394]: reading failed
Feb 12 12:37:45 io snapperd[3394]: THROW: stat on info directory failed
Feb 12 12:37:45 io snapperd[3394]: reading failed

Any ideas?

Thanks,

Robert

Other Discussions

StephenB
Feb 12, 2018
wrote:

creating test share & manual snapshot works

That suggests that if a better solution doesn't emerge, that a brute-force approach should work.

create a temp share (matching the access settings)

copy the files into it (perhaps with a backup job)

delete the original share

rename the temporary share to match the original

Have you checked to see if this issue affects all your shares, or if it only affects some of them?