Hi all!
I compiled tde 14.0.12 on 32 bit slackware (mostly 15.0, but actually upgraded from much earlier versions) via Ray-V Slackbuilds and desktop works ok.
But today I tried to copy 4.3 gb file from my home dir open in one konqueror tab into media/sdc1 (newly inserted usb flash drive) open in another tab, by selecting two files, and then selecting 'copy' from their context menu, and then switching tab and pasting files there.
I was surprized to see error on bigger file, one with 4.3 GB in size, while smaller file (2GB) copied ok. I copied bigger file with mc ok.
I wonder if this behaviour just comes from miscompilation (missing LARGEFILE_SOURCE ? ) or issue might be deeper ?
unless you've reformatted your usb drive, the limitation might be in it.
dep Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/
On Fri, Oct 21, 2022 at 11:48 AM, Andrew Randrianasulu randrianasulu@gmail.com wrote:
Hi all!
I compiled tde 14.0.12 on 32 bit slackware (mostly 15.0, but actually upgraded from much earlier versions) via Ray-V Slackbuilds and desktop works ok.
But today I tried to copy 4.3 gb file from my home dir open in one konqueror tab into media/sdc1 (newly inserted usb flash drive) open in another tab, by selecting two files, and then selecting 'copy' from their context menu, and then switching tab and pasting files there.
I was surprized to see error on bigger file, one with 4.3 GB in size, while smaller file (2GB) copied ok. I copied bigger file with mc ok.
I wonder if this behaviour just comes from miscompilation (missing LARGEFILE_SOURCE ? ) or issue might be deeper ?
пт, 21 окт. 2022 г., 18:48 Andrew Randrianasulu randrianasulu@gmail.com:
Hi all!
I compiled tde 14.0.12 on 32 bit slackware (mostly 15.0, but actually upgraded from much earlier versions) via Ray-V Slackbuilds and desktop works ok.
But today I tried to copy 4.3 gb file from my home dir open in one konqueror tab into media/sdc1 (newly inserted usb flash drive) open in another tab, by selecting two files, and then selecting 'copy' from their context menu, and then switching tab and pasting files there.
I was surprized to see error on bigger file, one with 4.3 GB in size, while smaller file (2GB) copied ok. I copied bigger file with mc ok.
ooops, mc also errored out saying file too big (because ventoy created fat32 vol without any option to change this...). Still a bit more informative error than konqueror give me. Also, option to delete incomplete file in such case will be nice ....
I manually (via gparted) formatted second partition on this drive as ntfs and .... konqueror said my pmount does not have 'p' option!
guest@slax:~$ pmount -V pmount from util-linux 2.37.3 (libmount 2.37.3: btrfs, mtab, namespaces, assert, debug)
manually mounted with ntfs3 kernel driver from 5.19.8
sorry for one wrong bugreport, but pmount bug might be real after all?
I wonder if this behaviour just comes from miscompilation (missing LARGEFILE_SOURCE ? ) or issue might be deeper ?
On Fri, 21 Oct 2022 19:15:19 +0300 Andrew Randrianasulu randrianasulu@gmail.com wrote:
I manually (via gparted) formatted second partition on this drive as ntfs and .... konqueror said my pmount does not have 'p' option!
guest@slax:~$ pmount -V pmount from util-linux 2.37.3 (libmount 2.37.3: btrfs, mtab, namespaces, assert, debug)
manually mounted with ntfs3 kernel driver from 5.19.8
sorry for one wrong bugreport, but pmount bug might be real after all?
Is the volume encrypted? pmount's -p option's long form is --passphrase .
If there's no encryption present, I'd bet on the issue being with the combination of pmount and ntfs. In-kernel ntfs support was near-useless prior to 5.15, and as far as I can determine, pmount development is dead (I can't find a source repository, and Gentoo is still shipping the same base version it was ten years ago with a few patches overtop), so it may never have caught up with the in-kernel changes.
If you need this drive readable on a Windows system, try formatting it in exfat (check your pmount to make sure it's been patched for exfat first). Otherwise, just format in the ext# of your choice.
E. Liddell