When the target NTFS file system is being mounted at https://github.com/ValdikSS/windows2usb/blob/master/windows2usb#L199, mount (as well as mount -t ntfs -o rw) would mount file system in read only mode. Yet if i do it via ntfs-3g helper directly (mount.ntfs or mount.ntfs-3g) everything works as expected.
I don't have a good fix for it, but would be willing to dig this deeper should somebody has any ideas on how to fix it.
When the target NTFS file system is being mounted at [https://github.com/ValdikSS/windows2usb/blob/master/windows2usb#L199](), `mount` (as well as `mount -t ntfs -o rw`) would mount file system in read only mode. Yet if i do it via ntfs-3g helper directly (`mount.ntfs` or `mount.ntfs-3g`) everything works as expected.
I don't have a good fix for it, but would be willing to dig this deeper should somebody has any ideas on how to fix it.
I suppose with mount -t ntfs kernel NTFS driver is used, which is simple and does support writing to the FS.
In most distros mouting NTFS is done by ntfs-3g. Could it be you have misconfigured system?
I suppose with `mount -t ntfs` kernel NTFS driver is used, which is simple and does support writing to the FS.
In most distros mouting NTFS is done by ntfs-3g. Could it be you have misconfigured system?
Yeah, i believe you're right. I do have both kernel module and ntfs-3g on machine where i ran into the issue. The fact that mount -t ntfs -o rw does succeeds with 0 result code, but just silently mounts it in read-only seems wrong to me.
Guess there is little value in accounting for such odd case here. Please close this as needed. And much thanks for the thing in the first place (and modded BIOS too) :)
Yeah, i believe you're right. I do have both kernel module and ntfs-3g on machine where i ran into the issue. The fact that `mount -t ntfs -o rw` does succeeds with 0 result code, but just silently mounts it in read-only seems wrong to me.
Guess there is little value in accounting for such odd case here. Please close this as needed. And much thanks for the thing in the first place (and modded BIOS too) :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When the target NTFS file system is being mounted at https://github.com/ValdikSS/windows2usb/blob/master/windows2usb#L199,
mount(as well asmount -t ntfs -o rw) would mount file system in read only mode. Yet if i do it via ntfs-3g helper directly (mount.ntfsormount.ntfs-3g) everything works as expected.I don't have a good fix for it, but would be willing to dig this deeper should somebody has any ideas on how to fix it.
I suppose with
mount -t ntfskernel NTFS driver is used, which is simple and does support writing to the FS.In most distros mouting NTFS is done by ntfs-3g. Could it be you have misconfigured system?
Yeah, i believe you're right. I do have both kernel module and ntfs-3g on machine where i ran into the issue. The fact that
mount -t ntfs -o rwdoes succeeds with 0 result code, but just silently mounts it in read-only seems wrong to me.Guess there is little value in accounting for such odd case here. Please close this as needed. And much thanks for the thing in the first place (and modded BIOS too) :)
What distro do you use?
That happened on NixOS 20.03. Before that i ran it successfully on a Gentoo with kernel without NTFS module.
Should be fixed in new version.