0 Byte File, FIle System Corrupted

[Ktel]

I recently upgraded to ifl 3.64. I installed it on Linux so I don't have to reboot to make a backup.
I haven't used it much yet but I did make at least one successful back up.
However, on two other occasions the backup completed and said it was successful but when I quit the program and looked where the backup file should be it wasn't there. I discovered I lost usable drive space equivalent to what the backup would take up. Yet I could not find the file. I went into imagel and it showed the file but with a size of 0 bytes. In both cases I had to repair the file system. One back up was from an internal NVME ext4 to an internal 5.25" SATA HDD NTFS. The other back up was from an internal NVME ext4 to an external USB NVME ext4.
Any ideas what could be going on?
Thank you.

[TeraByte Support]

You shouldn't save using file direct to a mounted file system, instead use file os.

[Brian K]

Ktel,

I'm confused. Which OS were you backing up? The Linux OS? I was under the impression we shouldn't backup the Linux partition by using the installed IFL, as the Linux partition isn't locked.

[Ktel]

"You shouldn't save using file direct to a mounted file system, instead use file os."

I'm not sure what you are saying there.

[Ktel]

"I'm confused. Which OS were you backing up?"

In the NVME to HDD case I was backing up an internal storage NMVE(non-system) to the HDD.
In the other case I was backing up the Linux OS system running the backup program to an external USB-C NVME. I did it all the time on Windows.

[Brian K]

. I did it all the time on Windows.

Windows can be locked with VSS and PHYLock. There is no locking for a Linux partition.

[Ktel]

I found further explanation in the manual.
The back up worked when I did File(OS).
Thanks for the guidance.

Image for Linux User Manual page 45.

File (Direct) – This option allows you to directly save the image file(s) to a
folder on a hard drive, bypassing the Linux OS file services. Supported
partitions can be accessed, including unmounted partitions and those in the
EMBR not loaded into the MBR. In most cases, when using physical drives
attached to the system, it’s easier to use File (Direct), especially when using
the Image for Linux boot media.
Note: Do not save your image to the same partition you are backing up.

File (OS) – Choose this option to use the Linux operating system file
services to save the image files. Use this option to browse mounted
partitions or network shares just as if you were browsing in Linux outside of
Image for Linux. You won’t be able to browse a partition or share that’s not
mounted, nor will you be able to access partitions not loaded into the MBR.

[Brian K]

I get it now.

Partition A was mounted in IFL. It will be the storage partition for backups.
Partition B was a WinPE partition.
A backup of partition B was created using File (Direct)
A backup of partition B was created using File (OS)

Partition A was not unmounted. Computer was restarted into Windows. Both backups were in partition A. Correct size.

The backup created by File (Direct) couldn't be opened by TBIView.
Booted into IFL again. The backup created by File (Direct) couldn't be seen when attempting a restore. It couldn't be seen in Partition Work, Edit File either.

Booted back into Windows. The backup created by File (Direct) couldn't be seen but it was taking up space.

[Brian K]

Test repeated. Partition A was mounted in IFL. A backup of partition B was created using File (Direct).

This time, Partition A was unmounted.

Computer was restarted into Windows. The backup could be opened in TBIView and didn't disappear after a restart.