Second try on LEGACY computer: I make a script based on cp command.
I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. First disque root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 Stats by df command a@b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2000625 Title: cp command loop when using ntfs3 package Status in e2fsprogs package in Ubuntu: New Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. See the rest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2000625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
