|
Post by Georg Eschenbach on Mar 26, 2008 3:37:55 GMT 7
Hi,
I have seen that post from Falk but I "thought" (or better: "wished") that it would be done with the changes of the files like quarx has written some posts before.
The question is: does it make sense to switch quta off or is there any chance to prevent rc.quota from writing into raid.db. or can the time step be changed from 5 minutes to lets say 24 hours? I havenĀ“t found the time step "5 minutes" when editing rc.quota, if so, I had tried to change it.
Greetings George
|
|
|
Post by Georg Eschenbach on Mar 28, 2008 16:43:12 GMT 7
Hello to all of you.
I have made all changes like QUARX has decribed.
In the meantime I have switched all quota completely OFF
Thanks to CLAQ I have found the cronjob for writing to rc.quota, which could be editied and changed from "every 5 minutes" to "every 720 minutes" for example.
I have switched off Twonkymedia module as well as Pureftp module. The only modules, which are still running ars sshd and sysuser.
And still my Seagate ST 31000340NS drives keep on spinning.
Any more ideas?
Greetings George
|
|
|
Post by fajo on Apr 20, 2008 21:34:45 GMT 7
The next FW release seems to finally fix the spin down issue. The Samba files will move to /var and the quota update interval will become 12 hours. The only thing that could prevent disks from spinning down then are addons (modules).
/Falk
|
|
|
Post by rainerstratmann on Apr 21, 2008 0:21:28 GMT 7
Hello to all,
fajo is right ;D
I got an email from Thecus:
"Hi Rainer,
We do have the beta version firmware which solve spin down issue, but due to beta version does not approve by QA team,..."
So waiting for a short time and we will get it..
Rainer
|
|
clag
New Member
Posts: 21
|
Post by clag on Apr 24, 2008 18:31:30 GMT 7
Hi,
the support talk something about the date when the final will relaesed ?
clag
|
|
|
Post by rainerstratmann on Apr 25, 2008 19:57:30 GMT 7
Hi, the support talk something about the date when the final will relaesed ? clag I asked them for the date yesterday and got an answer quickly: End of May will the final be released!!Greetings Rainer
|
|
|
Post by peanuts on Apr 26, 2008 2:44:44 GMT 7
I asked them for the date yesterday and got an answer quickly: End of May will the final be released!!Did they mention the year?
|
|
|
Post by schumi on Apr 28, 2008 14:24:31 GMT 7
Hi together,
I don'n know why, but I am using f/w 2.00.04 with 3 x 1TB RE2-GP from WD in RAID5 and the disks spin-down perfectly.
When I wait a certain time and access the NAS (either NSF or CIFS share) I can hear the disks spin-up again one by one. I have tested it with 30 min. and 120 min.
The only module I have installed is TwonkyMedia. I have nothing modified on the NAS by command-line.
Regards
schumi.
|
|
clag
New Member
Posts: 21
|
Post by clag on Apr 29, 2008 4:49:44 GMT 7
Hi schumi,
I think it is important to know in what network enviroment the 5200 runs. you can tell us a little about this? Is there an DomainController? the main problem comes up, if the NASbox run in a workgroup.
so long clag
|
|
|
Post by schumi on May 1, 2008 3:25:27 GMT 7
Hi clag,
There is no DomainController in my network environment. The N5200Pro is just a file server with some NFS and CIFS shares containing all my MultiMedia (video/audio/pictures) files and documents. It is connected to a Netgear 8-port GBit switch that is connected to a WLAN router AVM7270. The WLAN router provides the DNS server. The N5200Pro runs with static IP.
I hope this helps.
Regards
schumi.
|
|
|
Post by drewy on May 7, 2008 3:05:03 GMT 7
I've just noticed that the script I posted some time ago: #!/bin/sh # pdrew 2-feb-08 #change samba parameters if an effort to get disk spindown working on thecus 5200pro #set up smb.conf how we want it! while ! ps | grep -v grep | grep smbd > /dev/null do sleep 5 done sed -e 's/local master = yes/local master = no/g' /tmp/smb.conf > /raid/smb.conf.tmp sed -e 's/lock directory = \/raid\/data\/tmp\/var/local master = \/tmpfs\/var/g' /raid/smb.conf.tmp > /tmp/smb.conf #restart samba without rebuilding smb.conf # stop samba kill -15 `ps | grep smbd | awk '{print $1}'` kill -15 `ps | grep nmbd | awk '{print $1}'` kill -15 `ps | grep winbindbd | awk '{print $1}'` sleep 2 # start samba /opt/samba/sbin/smbd /opt/samba/sbin/nmbd /opt/samba/sbin/winbindd contains a typo: sed -e 's/lock directory = \/raid\/data\/tmp\/var/local master = \/tmpfs\/var/g' /raid/smb.conf.tmp > /tmp/smb.conf should be: sed -e 's/lock directory = \/raid\/data\/tmp\/var/lock directory = \/tmpfs\/var/g' /raid/smb.conf.tmp > /tmp/smb.conf Despite this, my disks have been spinning down just fine. So I assume setting local master = no is enough..... Anyway just thought I should correct my mistake
|
|
|
Post by N5200user on May 10, 2010 3:29:00 GMT 7
... # stop samba kill -15 `ps | grep smbd | awk '{print $1}'` kill -15 `ps | grep nmbd | awk '{print $1}'` kill -15 `ps | grep winbin dbd | awk '{print $1}'` ... Small correction: # stop samba kill -15 `ps | grep smbd | awk '{print $1}'` kill -15 `ps | grep nmbd | awk '{print $1}'` kill -15 `ps | grep winbin dd | awk '{print $1}'`
|
|