Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Won't close HUGE file after transferring #121

Open
Ahadrp opened this issue Sep 3, 2024 · 2 comments
Open

Won't close HUGE file after transferring #121

Ahadrp opened this issue Sep 3, 2024 · 2 comments

Comments

@Ahadrp
Copy link

Ahadrp commented Sep 3, 2024

I was transferring an iso file (~1.5GB), then I realize the file is not closed yet:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mount.ntf 153017 root 20w REG 259,2 1541406720 64 /media/path/a.out
mount.ntf 153055 root 20w REG 259,2 1541406720 64 /media/path/a.out
mount.ntf 153093 root 20w REG 259,2 1541406720 64 /media/path/a.out

Well, there are two questions:

  1. Why there are three processes?
  2. Why the file didn't close?!
@unsound
Copy link
Member

unsound commented Sep 3, 2024

I'm as confused about this as you are. What is /media/path/a.out? Can you issue the command stat /media/path/a.out and post the output?

@Ahadrp
Copy link
Author

Ahadrp commented Sep 4, 2024

I'm as confused about this as you are. What is /media/path/a.out? Can you issue the command stat /media/path/a.out and post the output?

Well, being in rush made me not to be clarify!

By saying /media/path/a.out I mean the [.iso] file.

For more explenation, let me talk about a scenario: I got two ntfs filesystems: A and B.

I just transferred the an .iso file to A and then move it to B. Well, I thought the transference happened successfully, so I just removed the .iso file from B. But here is the result:

  • in the B filesystem:

  • .fuse_hidden0000000300000001

and when I looked at the fd(s) at the mount point process of A filesystem, I realized that the file is not transferred, and the link which is referring to transference of .iso to B is beeping to red and white:

  • 2425 is the mount process of A
$ ls -la /proc/2425/fd
 total 0
dr-x------ 2 user user 0 Sep 4 15:34 . 
dr-xr-xr-x 9 user user 0 Sep 4 15:34 .. 
lrwx------ 1 user user 64 Sep 4 15:34 0 -> /dev/pts/0 
lrwx------ 1 user user 64 Sep 4 15:34 1 -> /dev/pts/0 
lrwx------ 1 user user 64 Sep 4 15:34 2 -> /dev/pts/0 
lrwx------ 1 user user 64 Sep 4 15:34 3 -> /media/A/a.iso 
lrwx------ 1 user user 64 Sep 4 15:34 4 -> /media/B/.iso [this is beeping. as I mentioned, I just removed it from B]

I'm sure that the transference is finished at my side, so:

  1. Why is the transition to A is not finished (socket is still open)?
  2. Why is the transition from A to B is not finished?

It's good to mention that this just happens on huge files (1.5GB> in my tests)

Using the Rocky-Linux-8 The ntfs-3g version: ntfs-3g-2022.10.3-1.el8.x86_64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants