From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: full_page_writes = off? |
Date: | 2007-12-02 20:58:56 |
Message-ID: | Pine.GSO.4.64.0712021528290.2007@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
On Sat, 1 Dec 2007, Tomasz Ostrowski wrote:
> You can also use "hdparm -I" to check this - look for a "Write
> caching" in "Commands/features" section. If it has a "*" in front
> then it is enabled and dangerous.
Right; using -I works with most Linux hdparm versions:
# hdparm -V
hdparm v6.6
# hdparm -I /dev/hda | grep "Write cache"
* Write cache
# hdparm -W 0 /dev/hda
/dev/hda:
setting drive write-caching to 0 (off)
# hdparm -I /dev/hda | grep "Write cache"
Write cache
While being able to check the state with -W only works in very recent
ones.
The best way to make this change permanent varies depending on your Linux
distribution.
Also: nowadays many SATA disks appear as SCSI devices like /dev/sda. In
some cases I believe you can use a recent hdparm on them anyway, in others
I've had to use sdparm instead. Several of the examples at
http://sg.torque.net/sg/sdparm.html show how to manipulate the Write Cache
Enabled (WCE) status similarly to the above on SCSI devices.
> I don't know how to check it on BSD.
In FreeBSD I believe you use atacontrol to check the settings, and you can
make the changes permanent by fiddling with the /boot/device.hints file.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-12-02 21:17:34 | Re: About contrib modules |
Previous Message | Tom Lane | 2007-12-02 19:21:31 | Re: [PATCHES] Partition: use triggers instead of rules |
From | Date | Subject | |
---|---|---|---|
Next Message | Rainer Bauer | 2007-12-02 21:19:01 | Re: Cluster using tablespaces? |
Previous Message | Usama Dar | 2007-12-02 20:58:54 | Re: One or more tables? |