August 14, 200817 yr Posting them here in a separate thread since they are old but no comment on if and when they are getting fixed ... aka they have been lost in the sea of posts. Bug 1 ==== If you have say this structure: /mnt/disk1/Test /mnt/disk1/test /mnt/disk2/Test The case causes havoc with the share names. Stuff looks like its gone missing from the big share and renaming the test to Test causes the whole big share to go offline. If you have say "test" and "Test" on the same disk Linux sees them as distrinct folders (as it should) but samba sees them as one. This means that if test is empty but Test has 100 files in it samba shows these files in both test and Test. Whole heaps of confusion for end users here. Bug 2 ==== If you have a shell open in mount or pehaps a samba share open (cant repliatce this easily but it does happen) when you stop the array ALL the disks say unformatted and the format button appears. HUGE potential for data loss here. Even if no data loss saying the disks are unformatted is just incorrect.
August 14, 200817 yr Bug 2 ==== If you have a shell open in mount or pehaps a samba share open (cant repliatce this easily but it does happen) when you stop the array ALL the disks say unformatted and the format button appears. HUGE potential for data loss here. Even if no data loss saying the disks are unformatted is just incorrect. Confirm and agree with you That`s very annoying and happenes not only with a shell opened. This may be any application accessing the disk (like uShare in my case). The STOP button should kill all the processes writing/reading from the disk before unmounting.
August 15, 200817 yr Re: BUG 2 - Agree 100%, I think the powerdown script handles it in a satisfactory manner. Perhaps tom could implement the same logic with fuser so he could kill processes on the filesystem. I see this becoming more of an issue as we start to use our unRAID servers for more then simple filesharing.
August 22, 200817 yr re: Bug 1 - this is quite a large can of worms & we'll need to study this further. reg: Bug 2 - this is a known issue & on our list to fix with next release.
March 3, 200917 yr Author re: Bug 1 - this is quite a large can of worms & we'll need to study this further. reg: Bug 2 - this is a known issue & on our list to fix with next release. Any update on these?
March 3, 200917 yr re: Bug 1 - this is quite a large can of worms & we'll need to study this further. reg: Bug 2 - this is a known issue & on our list to fix with next release. Any update on these? I'm running 4.4.2 and encountered bug 2 a few days ago. I left a shell session logged in on /mnt/Disk2 and stopped the array to power down, and Disk1 showed as unformatted. After a brief panic attack, I check the Open Files in the unMenu System Info which showed the directory in use. So I saved a syslog, closed the shell session, stopped the array, rebooted and all was well.
March 3, 200917 yr I have a little extension that will be added to the unRAID-Web soon. "Safer Shutdown" will give you a button that does a safer, controlled shutdown, that includes: - displays a list of what files/directories are open or in use, and ask you if you want to proceed. - ability to designate a user-defined script to run BEFORE starting the shutdown. - ability to designate a user-defined command to run BEFORE shutdown that must return a success - gracefull kill of processes with open files - clean stop of the array, with error-checking and reporting... and graceful recovery if stop was unsuccessful - ability to designate a user-defined script to run AFTER stopping the array - ability to designate a user-defined command to run AFTER stopping the array that must return a success - then finish the shutdown/reboot. Any other suggestions?
March 9, 200917 yr Author .... Bug 2 ==== If you have a shell open in mount or pehaps a samba share open (cant repliatce this easily but it does happen) when you stop the array ALL the disks say unformatted and the format button appears. HUGE potential for data loss here. Even if no data loss saying the disks are unformatted is just incorrect. Confirmed bug still exists in 4.5-beta2
March 24, 200917 yr Author .... Bug 2 ==== If you have a shell open in mount or pehaps a samba share open (cant repliatce this easily but it does happen) when you stop the array ALL the disks say unformatted and the format button appears. HUGE potential for data loss here. Even if no data loss saying the disks are unformatted is just incorrect. Confirmed bug still exists in 4.5-beta3
Archived
This topic is now archived and is closed to further replies.