Is anyone else having smb issues/have they been fixed?
If i only read from the device everything works fine. if i attempt to write, things get corrupt. It appears the folder tree is not being enumerated correctly on writes. as every file is believed to existing in every folder (based on windows saying already exists, if you try to copy from one folder to another)
can someone with an tarq login bump the ticket. I feel its warranted for the following reason
1. Reads work correctly thus an unwitting user might not know there is an issue till its to late
2. destructive damage appears to happen on write, at least on windows, before the error is even returned the file is damaged / destroyed - if it cant be fixed its worthy of a revert
smbd is just messed up in everything later than r47531 which is what I run on the EA8500 units.
I reckon it will be fixed whenever....
NOT really sure why BS just don't roll it back.
This is what screwed it ---> https://svn.dd-wrt.com/changeset/47534
I am also waiting for resolving this issue. last working well samba for me Firmware: DD-WRT v3.0-r47528 std (10/10/21)
I rolled back to 47528 (using EA8500), but I was still getting corruption error with NTFS drives (not sure if that is related).
Also, I noticed there were still plenty of error messages if you run "dmesg" from putty as each write operation initiated from any windows 10 client had ~10 errors. I tried mounting an ext2 thumb drive and it produced the same error messages on write from windows.
I didn't get corrupted drive error with ext2, but I removed it after a day. If I attempt a copy within linux between samba/CIFS drives, those seemed to be fine.
Here is a sample message that I posted in another thread on EA8500. I noticed 8-10 such messages each time I copied a file from windows to the shared drive.
"ksmbd: Unsupported addition info: 0x20)"
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Nov 23, 2021 17:48 Post subject:
People are not looking at the larger picture; I'll venture to say that we need more folks cloning the github and looking at upstream code repos and submitting pull requests. This firmware project is (mostly) a one-man show and anyone who has looked deep enough knows that some packages fall behind upstream updates and may already have documented issues. _________________ "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
I figured it was not an issue, but I was trying to backup around 10k files and noticed a lot of activity.
Just out of curiosity, I installed entware and used samba4 server instead of ksmbd. I think it worked fine without any of those errors.
Does anyone have any recommendations around syncing directories? Is rsync a good option to run between the EA8500 router and another linux server? (the other one is an old NAS with just one disk and less memory than this router, so I am looking to maintain a reliable backup automatically).
Also if I make the initial backup using windows (since that seems to be faster with ~50-70MB/s average vs 30MB/s when run in router as a copy command), can I sync the same folders using rsync for incremental backups? (which should be much smaller volume <1% of the data)
Last edited by mark74 on Tue Nov 23, 2021 19:08; edited 1 time in total
@bushant i agree about reading the build threads, however doing so would not prevent this issue as there indication that samba is broken to the extent that any write will kiss your file your writing to goodbye.
I had to go back to an old backup of a corrupted file and lose a few days because of this. Granted i should have more frequent backups, but this is a really serious bug. I would have preferred smb be completely inoperable than have this
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Nov 23, 2021 21:24 Post subject:
"Mission critical" things shouldn't be left to this since ksmbd is in constant development, as is wsdd2. Again, both are likely not 100% sync'd up with upstream, as I've alluded to elsewhere. In fact, there is smbd and smbd-next directories in the DD-WRT repo, and I have not seen which is in use where and back-tracked to see what is what.
Honestly, all the bickering doesn't solve a damn thing, and quite frankly, it makes folks who wish to contribute to solving issues not want to bother. People should remember that, myself included. _________________ "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
