xfce, thunar, flash usb drive was corrupted after interrupting copy operation

xfce, thunar, after interrupting copying iso to my ntfs usb flash drive was corrupt and folder are wiped
1. copying ghostbsd iso via thunar
2. thunar not copyng but showing endless "queue'
3. i am interrupt copying by cancel operation at coping dialog window
4. but thunar still try copying at background
5. i am kill thunar process
6. after i am look at usb flash drive disk usage, its decreased, no any files at flash but place is occupied of something. Also all files that was in target folder are wiped!?
6. result-reformatting flash drive
7. verdict-freebsd is very glichy and full of bugs os that not ready for desktop usage.
end.
 
… last impression from fbsd … now i am ghostbsd …

So, the robustness of FreeBSD works for you. In case you missed it, at the home page:

1727457450553.png
 
xfce, thunar, after interrupting copying iso to my ntfs usb flash drive was corrupt and folder are wiped
1. copying ghostbsd iso via thunar
2. thunar not copyng but showing endless "queue'
3. i am interrupt copying by cancel operation at coping dialog window
4. but thunar still try copying at background
5. i am kill thunar process
6. after i am look at usb flash drive disk usage, its decreased, no any files at flash but place is occupied of something. Also all files that was in target folder are wiped!?
6. result-reformatting flash drive
7. verdict-freebsd is very glichy and full of bugs os that not ready for desktop usage.
end.
File transfers are much safer and better handled on FreeBSD than on Windows, and you can even enhance it in Thunar (or XFCE) settings.
That said, none of Windows, FreeBSD or any OS will be bulletproof if you force kill the stuff that's copying, period. And you're not safe from a hardware disk failure...
Starting from your way of thinking, you can also say it's FreeBSD, Windows, or anything fault if you get corruption after power loss...
 
File transfers are much safer and better handled on FreeBSD than on Windows, and you can even enhance it in Thunar (or XFCE) settings.
That said, none of Windows, FreeBSD or any OS will be bulletproof if you force kill the stuff that's copying, period. And you're not safe from a hardware disk failure...
Starting from your way of thinking, you can also say it's FreeBSD, Windows, or anything fault if you get corruption after power loss...
Totally opposite opinion here with my first experience using FreeBSD, I never had such problems with windows and even linux

FreeBSD is unsafe for using at desktop
 
Totally opposite opinion here with my first experience using FreeBSD, I never had such problems with windows and even linux

FreeBSD is unsafe for using at desktop
OK, I have to find a way to tell my laptop that it's impossbile it's working so well because "FreeBSD is unsafe for using at desktop". It's impossible that everything works (almost) out of the box. Thanks for letting us know and now go enjoy you GhostBSD.
 
xfce, thunar, after interrupting copying iso to my ntfs usb flash drive was corrupt and folder are wiped
1. copying ghostbsd iso via thunar
Why are you using a complex tool when a simple one would have been sufficient? I would use dd.

2. thunar not copyng but showing endless "queue'
Have you considered hardware problems? Did you check the output of dmesg or /var/log/messages? USB sticks are famously unreliable and depending on the host OS.

3. i am interrupt copying by cancel operation at coping dialog window
4. but thunar still try copying at background
I have no idea whether thunar has bugs. Given that it is a GUI app, it has to be internally asynchronous, and killing a child process asynchronously is not easy. Again, this is an argument for a simpler tool: If you use dd, and hit control C or control-\, you know which signal got delivered to the process.

5. i am kill thunar process
Did you check what state the process was, before and after?

6. after i am look at usb flash drive disk usage, its decreased, no any files at flash but place is occupied of something. Also all files that was in target folder are wiped!?
All files are wiped because you copied to the whole flash drive, not to a partition.

The copy operation probably started by writing a partition table or GPT to the flash drive, which occupies the space, even if the copy has not completed.

6. result-reformatting flash drive
You begin a large and atomic copy operation. You interrupted it, leaving it incomplete. Having to reformat (or recopy) makes perfect sense.
 
Why are you using a complex tool when a simple one would have been sufficient? I would use dd.
its habit use xfce after using windows,

i use easy2boot frash drive for multyboot tool for different iso,

what simple solution you suggest? tottaly not use DE, and use naked tty? no software no problems? maybe i come to that philosophy but not yet.

now i am at ghostbsd with mate de and i like it me more than xfce for the present moment with ghostbsd, at linux i had no seen so many issues with xrce
 
The copy operation probably started by writing a partition table or GPT to the flash drive, which occupies the space, even if the copy has not completed.
but why others iso files from this folder is disappearing after interrupting copy but space was occupied?
 
what simple solution you suggest? tottaly not use DE, and use naked tty? no software no problems?
That is exactly what I suggest. You want to copy something to a USB stick: figure out what file system you want on the USB stick, or whether the thing you are copying is a complete file system image (most boot iso images are). Then use the simplest tool for doing the copy: for a single file, cp; for a directory or directory tree, rsync; for a file system image, dd.

dd is not trivial to use, because its command line parameters are unusual (they are actually an in-joke that would take too long to explain, you can find it on the web). But a quick look at "man dd" or some other documentation will make it easy.

And then, if you have problems like you did with your original post, the problems will be easy for yourself or for others to diagnose and fix.
 
And then, if you have problems like you did with your original post, the problems will be easy for yourself or for others to diagnose and fix
1. problems not for me but xfce+freebsd
2. how by myself i can resove it!? i am just user not creator of those things.
 
Back
Top