Creating hard link to timeshift file file failed,

[Stubn]

Hi
We filled our V2 hdd yesterday. After making some space I am now getting an error.

*message box contents*
Creating hard link to timeshift file failed!
The file system used for timeshift must support hardlinks

/media/hdd/timeshift/
[errno 17] File exists


Any ideas please?

[prl]

Strange that it's a "File exists" error.

Presuming that it's a persistent problem, can you go to the FileCommander (MENU>Sources / Files), and then navigate to the /media/hdd/timeshift directory, and say what you see there?

[Stubn]

Thanks for your reply.
Yes it’s persistent, I see it whenever I change channels or startup.

Screenshots attached.

[Stubn]

And timeshift seems to be working despite the error

Just realised I’m using the beta. This post is in the wrong folder. Can it be moved?

20200405

[MrQuade]

Do you still have an SD card plugged into the V2?

Do you normally use that for timeshifting?

If a SD card is fitted, then this is usually mounted as the "hdd".

Just wondering if the filled hdd caused the timeshift location to jump somewhere else somehow, and that other location may not be formatted with a hardlink-capable filesystem?

[Stubn]

I use a 1TB portable hdd for both recordings and timeshift (I think). I wondered about the location too as I’ve seen it move before when trying to leave a thumb drive connected.

It seems to be right as some of the files were modified today When I check file commander. As in the photo earlier. Not all the timeshift files have today’s date though... old versions?

[MrQuade]

Is the SD still fitted?

[peteru]

Have you tried turning it off and on again?

Long press POWER button to get to the shutdown menu option.

[Stubn]

Is the SD still fitted?

Sorry, i didnt actually answer that. No i dont have a SD fitted. it didnt come with one.

I checked the slot on the back anyway, and it looks empty. Is there somewhere else i should check?

[Stubn]

Have you tried turning it off and on again?

Long press POWER button to get to the shutdown menu option.

yes, i've done a long press shutdown, and also powered it off from the wall, after shutting down. I've done it a few times now.

[Grumpy_Geoff]

It seems to be right as some of the files were modified today When I check file commander. As in the photo earlier. Not all the timeshift files have today’s date though... old versions?

Are there still "old" (prior to today) pts_livebuffer_{n}* timeshift buffer files present in /media/hdd/timeshift? Assuming that's the value for setting 'Timeshift location' in Timeshift settings.

[prl]

I checked the slot on the back anyway, and it looks empty. Is there somewhere else i should check [for the microSD card]?

No, that's the only card slot.

[Stubn]

Are there still "old" (prior to today) pts_livebuffer_{n}* timeshift buffer files present in /media/hdd/timeshift? Assuming that's the value for setting 'Timeshift location' in Timeshift settings.

yes, there are some date/time stamped today and some around when we filled the HDD. See the picture, the ticks represent current files.

[MrQuade]

I'd disable timeshift. Then go and manually delete those old files using the file explorer.

[Grumpy_Geoff]

I'd disable timeshift. Then go and manually delete those old files using the file explorer.

I'd disable timeshift, zap to a new service to stop the writing of the current timeshift buffers, then delete all of the files.

It's interesting that there's not a complete set of pts_livebuffer_{n}.meta/eit/sc files.

[christas61]

I'm having exactly the same problem. My HDD is no where near full, the message just started the other day. Have tried everything suggested above. Timeshift works but you get the message every time you change channels.
Any thoughts?

[Stubn]

Thanks for the ideas.

I disabled timeshift. Zapped to a new channel and rebooted.

When I try to delete the files afterwards, the V2 does some sort of soft crash and quickly restarts.
I tried using a W10 laptop to delete the timeshift files without the V2 and it wouldn’t let me.

I then set the timeshift location to a new folder in the HDD and timeshift works (as it was anyway) and the pop up message stopped.

So, is there a way of deleting the locked/corrupted files?

[christas61]

I did what you suggested Andrew and it worked for me also. I was 5 minutes too early putting my original post up. Cheers

[MrQuade]

When I try to delete the files afterwards, the V2 does some sort of soft crash and quickly restarts.
I tried using a W10 laptop to delete the timeshift files without the V2 and it wouldn’t let me.

I then set the timeshift location to a new folder in the HDD and timeshift works (as it was anyway) and the pop up message stopped.

So, is there a way of deleting the locked/corrupted files?

You'll want to run a checkdisk over it.

Did you say you plugged it directly into a Windows machine? Is the disk formatted as NTFS? If so, you should probably do the checkdisk from the Windows machine.

[Stubn]

You'll want to run a checkdisk over it.

Did you say you plugged it directly into a Windows machine? Is the disk formatted as NTFS? If so, you should probably do the checkdisk from the Windows machine.

Yes I did plug it into a windows machine , and I’ll follow your suggestion.

Thanks

[peteru]

Hmmm, NTFS.

Maybe it's best if the code is changed back to explicitly exclude NTFS from the list of supported file systems for timeshift. If the NTFS drive is not unmounted cleanly, the Beyonwiz does not have a full fledged fsck to fix NTFS file system corruption.

Even though NTFS may have the features required for timeshifting, if the HDD can not be repaired, then it can not be properly supported. I think in terms of reliability, it's probably best if only ext4 is accepted as a timeshift file system.

[Stubn]

You'll want to run a checkdisk over it.

Did you say you plugged it directly into a Windows machine? Is the disk formatted as NTFS? If so, you should probably do the checkdisk from the Windows machine.

CHKDSK from my windows PC removed the files, i returned Timeshift to normal directory and was able to delete the now obsolete temporary location.