similar to: samba writes to disk each 5 minutes...

hi :) when using ext3, i can't get my hard disks to go to standby mode any more. i am using timeouts set by hdparm with 2.4.18 kernels. even when i issue a standby command manually, the disk spins up again after a few seconds. however, (to my knowledge) no user space program accessed this disk at that time. i suspect ext3's journal to be causing the disk accesses. is that possible?

On 11/11/19 10:46 AM, Leon Fauster via CentOS wrote: > Am 11.11.19 um 14:28 schrieb Stephen John Smoogen: >> On Sun, 10 Nov 2019 at 17:12, Robert Moskowitz <rgm at htt-consult.com> >> wrote: >>> >>> I just built a CentOS7 system on a Zotac NANO PC. >>> >>> I used a 320GB 2.5" HD I had sitting around and installed with Standard

Hai David, What you want is possible, i would do something like this. I've not tested it but read it, its a good pointer howto do this. Debian used systemd. Close your eyes Rowland.... ;-) Im still learning things about systemd, so if some sees things that needs to be corrected please tell us. To remember! Files in /etc/tmpfiles.d override files with the same name in

Okay, I've been chasing performance for a while now. I have no idea if I should be trying to get better performance or if I'm getting all I can out of my hardware. Here is the information: /sbin/hdparm -I /dev/hdd /dev/hdd: ATA device, with non-removable media Model Number: ST328040A Serial Number: 7BY034XB Firmware Revision: 3.07 Standards:

Hi May I ask for help with this again please? I’m trying to ensure that Samba writes its wins.dat file to tmpfs. I have added these mount commands to /etc/init.d/samba: case $1 in start) mount -t tmpfs tmpfs /var/run/samba mount -t tmpfs tmpfs /var/cache/samba /etc/init.d/nmbd start /etc/init.d/smbd start

Hello everybody, I am not using astdb (no func_db and app_db) so I am wondering why asterisk is always updating it. The interval of the update is not constant. Using lsof, I noted the intervals are somewhere between 1 minute to 12 minutes. The output of lsof says that asterisk, atd and crond processes were just active, just after the hard disk changed the state from standby to active/idle. I

I think you answered your own question. Samba (smbd) is a service. It is doing its job and ready to offer service at any time. Apparently this involves periodically accessing the disk. There is nothing wrong with this; it is normal operation. Samba won't work anyway when you are in standby, so you might as well stop it when you are done using it. PG > -----Original Message----- >

Am 11.11.19 um 14:28 schrieb Stephen John Smoogen: > On Sun, 10 Nov 2019 at 17:12, Robert Moskowitz <rgm at htt-consult.com> wrote: >> >> I just built a CentOS7 system on a Zotac NANO PC. >> >> I used a 320GB 2.5" HD I had sitting around and installed with Standard >> Partitions on XFS. >> >> The drive is spinning, nonstop. > > I would

Can someone please explain what's wrong here. And how to solve it. I run CentOS-4.1 MSI K8N Neo Platinum Athlon 3000 Seagate Barracuda 7200.7 S-ATA disc [root at amd64 kai]# /sbin/hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2808 MB in 2.00 seconds = 1402.81 MB/sec HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device Timing buffered disk reads:

Many thanks once again to those that responded to my original posting (and my follow up message) with information about Network UPS Tools, other Linux-based tools like rtcwake, and commercial UPS products. We have quite a bit more evaluation and testing work to do before a power fail protection method is selected.? I hope the discussion is as beneficial to others as it is to my organization.

I'd like to to put the hard drives in standby mode during periods of no activity. I'm just running a file server plus a couple small things on a Qube 3 from home, although the web stuff will increase it's still minimal. On my NetBSD systems I can use atactl to do this via: mount -u -o async,noatime,nodevmtime / mount -u -o async,noatime /usr atactl wd0 setidle 5 [wait a time]

Hi, I run a little router/firewall that also acts as a print server for the linux and win98 clients on the LAN. I have the harddisk configured so that if there is little activity, it spins down (hdparm -S 12 /dev/hda). I added smbd/nmbd today and with the two services running, the hard disk drive spins down but wakes up about every 12 minutes. Without the services, only a major event causes them

Hi there, I'm running a centos 5.2 (with a centos 5.3 kernel) on a box with a samsung 1To green edition, and this disk looks a bit slow to me and it's not recognized by hdparm : # hdparm -iI /dev/sda /dev/sda: HDIO_GET_IDENTITY failed: Invalid argument HDIO_DRIVE_CMD(identify) failed: Invalid argument # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2252 MB in 2.00 seconds =

On Mon, Feb 8, 2016 at 3:18 PM, <m.roth at 5-cent.us> wrote: > Chris Murphy wrote: >> DBAN is obsolete. NIST 800-88 for some time now says to use secure erase >> or enhanced security erase or crypto erase if supported. >> >> Other options do not erase data in remapped sectors. > > dban doesn't? What F/OSS does "secure erase"? And does it do

I''ve been doing some merge work between tools/ioemu and qemu upstream. I came across this commit: changeset: 11209:9bb6c1c1890a07885265bbc59f4dbb660312974e date: Sun Aug 20 23:59:34 2006 +0100 files: [...] description: [qemu] hdparm tunable IDE write cache for HVM qemu 0.8.2 has a flush callback to the storage backends, so now it is possible to implement

I believe I've posted before about one of the speed issues we were having, of backups taking many, many hours that should *not* take that long. My manager and I finally nailed it down to the h/d itself. Identical boxes, and he tried a backup of one system which took under two hours, while the same regular one rand nearly six. I'd been googling on and off for weeks, and this morning, ran

Hi all, When I ran the experiments to compare an application''s execution time in both a domU (named cctest1) and a native Linux machine (named ccn10), I noticed the application executes faster in domU. The host of the domU (named ccn9) and ccn10 are two nodes of a cluster and they have same hardware configurations. domU (cctest1) is created by exporting loopback files from dom0 on

Hi all. I have a CentOS server: CentOS release 5.7 (Final) 2.6.18-274.3.1.el5 x86_64 I have two SSD disks attached: smartctl -i /dev/sdc smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: INTEL SSDSA2CW120G3 Serial Number: CVPR13010957120LGN Firmware

It seems I can't smarm monitor disks on RAID controllers? I tried on several machines with two different controllers and on all I get this when starting up smartd: Jul 27 14:36:43 c1 smartd[5944]: Opened configuration file /etc/smartd.conf Jul 27 14:36:43 c1 smartd[5944]: Configuration file /etc/smartd.conf parsed. Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, opened Jul 27 14:36:43

Hi Gang, I recently rented a server at a datacenter with Centos 5.7 X64, Q9550 Processor, 8GB Ram, and dual 250GB SATA HDs (with 16mb cache). They had loaded it with KVM, and installed a 30-day trial of Virtualizor as the front-end for KVM. I was so impressed with how fasts the guests ran that I want to build a few of these machines for myself. I just installed one: same Q9550 processor, 4GB