It is just a pity, as it used to work well. In previous builds (I just do not remember it) the real size was shown and no problem with dirty drive or anything. I was just in hope all will work as it used to be, but better. Seems since half a year we are going a step back in matter of stability and improvement. I hope there will be one version that will fix it and for sure I won't update firmware anymore.
For me it is essential to use ntfs, so ext4 is sadly not an option. However, the ksmbd thing is something new to me. I am actually not into this and do not know how to install / use it instead.
There is nothing to install for ksmbd or wsdd2, those bits are internal to DD-WRT firmware for devices that feature network attached storage functionality via Samba. With Samba proper, Windows doesn't care what filesystem the network attached storage uses and the same is supposed to be true in respect to ksmbd. I don't understand why you would absolutely have to use NTFS. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
There is nothing to install for ksmbd or wsdd2, those bits are internal to DD-WRT firmware for devices that feature network attached storage functionality via Samba. With Samba proper, Windows doesn't care what filesystem the network attached storage uses and the same is supposed to be true in respect to ksmbd. I don't understand why you would absolutely have to use NTFS.
So how can I use ksmbd instead? I need NTFS as I use this device somethimes for data backups and other things. So if it is ext4 it might cause problems to some devices or they do not know how to use it properly.
Let's connect the dots. "Samba" in the webUI of DD-WRT official firmware releases for the most part IS ksmbd. Neither Linux, MacOS, Windows, nor any other client will give two shakes of a leg of concern about what filesystem is being used for your attached storage. It seems you are filled with FUD over something so benign and trivial. The sky is not falling. You were given options and a solution. Choose what you will. It is your network and your router. Thanks for listening and hopefully understanding. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sat Jul 23, 2022 19:50 Post subject:
Not for the most part, all is ksmbd afaik (the other components directories are there for gathering digital dust), filesharing shouldn't care about what the FS on drives are but it does something with it and its not bug free either, but if the FS handling or ksmbd is buggy or ntfs-3g or other 3rd party component in DD-WRT and such bugs need to be checked/reported upstream. DD-WRT afaik does not maintain any patches for most of them neitherntfs-3g nor ntfs3
There are some patches on ksmbd sub directory but no idea who maintains those, didn't go upstream to check if they exist there.
Just to let you know, no one here will report bugs reported here to the relevant 3rd party project(s), I would if I had time and the correct info to fill in a proper bug report, but sadly have neither. IF only we had more active developers who handled other areas, some projects I was part before, the devs usually submitted patches upstream, BS does it with ZFS for instance, maybe others like drivers and compression related stuff.
So after we determine where issue lies, if the report is not filed upstream according to their requirement for bug reports, it will remain a bug in DD-WRT no matter how many times those components are updated, unless of course they know about the bug from some other party and have fixed it, in such case its a happy coincidence.
I *think* what the OP means is that he sometimes needs to physically unplug the drive from the router [transport it somewhere else] and plug it into a windows machine. That is a pretty good reason to prefer NTFS...