Please bare in mind this may be a 3rd party component which is not directly developed by DD-WRT which is causing this.
Any other reports should be aggregated here.
Thanks for understanding.
Thx for your reply. To let u know, it can not be the 3rd party hardware. As it used to show it correctly in previous builds. Since a few weeks / builds it shows wrong.
When was the last time you ran a chkdsk on the drive while connected to a Windows PC? The "dirty drive" issue may or may not be completely fixed, and it's best to rule out all possibilities, however unlikely they are or not. The only development related to NTFS since the "last good build" seems to be to ntfs-3g, so maybe the update introduced a regression. Who knows. _________________ "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: 18 Mar 2014 Posts: 12877 Location: Netherlands
Posted: Thu Jul 21, 2022 9:20 Post subject:
You are reporting two problems:
About the disk size, is this a samba issue e.g. wrong reporting in windows? or a driver problem
compare:
hdparm -I /dev/sda1 (capital Isaac and assuming your disk is sda1)
fdisk -l (lower case leo)
About the TV not being able to see your samba share could be due to the fact that SMB1/Netbios is deprecated so older clients struggle
When was the last time you ran a chkdsk on the drive while connected to a Windows PC? The "dirty drive" issue may or may not be completely fixed, and it's best to rule out all possibilities, however unlikely they are or not. The only development related to NTFS since the "last good build" seems to be to ntfs-3g, so maybe the update introduced a regression. Who knows.
Actually, after every second or third reboot I need to perform a chkdsk by unplugging it and do it over a windows PC. However, in the past that was never the case, it was smooth.
So yes I guess the update introduced a regression. I hope it will be fixed in the up coming updates. However, I have been living with this issue for more than a year, it is really annoying.
About the disk size, is this a samba issue e.g. wrong reporting in windows? or a driver problem
compare:
hdparm -I /dev/sda1 (capital Isaac and assuming your disk is sda1)
fdisk -l (lower case leo)
About the TV not being able to see your samba share could be due to the fact that SMB1/Netbios is deprecated so older clients struggle
As already stated an NTFS disk becomes dirty easily after a reboot and especially after power loss, you then have to run chkdsk
This is for sure a samba issue. As many other reported on dd-wrt interface it shows the right size 5TB but on any samba client it shows wrong size. This issue was fixed in a previous release (I guess March 2022) and then it appeared again.
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Fri Jul 22, 2022 14:12 Post subject:
I have to agree that network client issues like this with features in DD-WRT aren't necessarily a DD-WRT problem. If the DD-WRT webUI reports correct information, that is the chief concern. So, reporting it here does not fix the upstream code that DD-WRT relies mostly on. I did notice some back 'n' forth on ntfs3 and an update to ntfs-3g in the public repo commits that may also be of note here. But again, that is usually dependent on 3rd party upstream code or in-house patches. Only way to pinpoint the regression is to step through undoing patches and updates or other research and such. or check upstream mailing lists / code repositories for reports, patches, and fixes submitted.
@egc: I know you don't use ksmbd in your community builds, so asking you to test these theories may be moot here. I'll see if the other working group wants to oblige, but we honestly have considered removal of Samba, Plex, and minidlna among other things from the picture altogether for the sake of performance and other options over "ridiculously unnecessary features". Anyway, hopefully there is a fix in sight soon enough. "In-house proof and bug testing over submission of incomplete work"... and these are a great group of folks, once you get past the nuances, lol. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 18 Mar 2014 Posts: 12877 Location: Netherlands
Posted: Fri Jul 22, 2022 15:16 Post subject:
kernel-panic69 wrote:
I have to agree that network client issues like this with features in DD-WRT aren't necessarily a DD-WRT problem. If the DD-WRT webUI reports correct information, that is the chief concern. So, reporting it here does not fix the upstream code that DD-WRT relies mostly on. I did notice some back 'n' forth on ntfs3 and an update to ntfs-3g in the public repo commits that may also be of note here. But again, that is usually dependent on 3rd party upstream code or in-house patches. Only way to pinpoint the regression is to step through undoing patches and updates or other research and such. or check upstream mailing lists / code repositories for reports, patches, and fixes submitted.
@egc: I know you don't use ksmbd in your community builds, so asking you to test these theories may be moot here. I'll see if the other working group wants to oblige, but we honestly have considered removal of Samba, Plex, and minidlna among other things from the picture altogether for the sake of performance and other options over "ridiculously unnecessary features". Anyway, hopefully there is a fix in sight soon enough. "In-house proof and bug testing over submission of incomplete work"... and these are a great group of folks, once you get past the nuances, lol.
Yes we have community build members still using old Samba3 and ntfs3g/fuse so basically the old stuff because he wants utmost stability and not the new shiny paragon ntfs3 kernel driver and ksmbd
I actually have now my R6400v2 running with ksmbd and the ntfs3 kernel driver.
the ntfs3 kernel driver is the one which is picky and flag a drive dirty after a power loss etc. which it is actually expected.
When using ext4 we have the built-in e2fsck which is easy to use (does it run automatically if it detects problems?)
When using ntfs we do not have chkdsk sot that you have to remove the drive and run it externally.
But hey this is Linux just use ext4 (and yes this is transparant for windows user running samba)
About ksmbd well that is a WIP, it is smal, lightweight and fast but not free of bugs
Actually the last few months it is usable.
Before that when copying large amounts of files (i.e. 1000 files several gig) it just blew up, that is improved.
The wrong reporting of size is a known problem for NTFS and several attempts have been made to address it.
So concluding ksmbd is OK if you are using ext2/4 as file system and have clients which use SMB2 (I use Xplore on my android phone which works well)
I have also a router running SAMBA4 that is really huge and a memory hog
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Fri Jul 22, 2022 16:17 Post subject:
Rather than post details here as the other working group has been a private venture, I will say that we have tackled plenty of ideas over the past couple of years or so. I know that sharing is caring and all, but certain nuances and dynamics within the constraints of this forum and project have prevented - or rather, made us unwilling - to do so. I'll refrain from further comment as it has no possibility of positive impact here. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Just don't use NTFS when it comes to data integrity.
This is simply a bad file system when it comes to power failures.
I can tell a little anecdote about this.
Many many years ago ... I have reinstalled my Windows.
(everybody knows it - by the way, it speaks for the quality of Microsoft products).
After several hours I was finally done and had my Windows installation set up again.
Then suddenly there was a power failure ... 15min later, the power was back ... the computer is just booting up and BANG the power was gone again.
After that the installation was broken again.
Was the last time in my life that I used Windows and NTFS on my own computer.
fucking windows crap
NTFS only supports metadata journaling
EXT3+4 support metadata + block journaling
Last edited by ho1Aetoo on Fri Jul 22, 2022 17:20; edited 1 time in total
