29%
23.03.2016
is just about one error per gigabit of memory per hour. The lower number indicates roughly one error every 1,000 years per gigabit of memory.
A Linux kernel module called EDAC, which stands for error
29%
30.11.2025
bandwidth measurements as follows:
Kilobytes are written as k or kb.
Megabytes are written as m or mb.
However, I'm more comfortable using kilobits and megabits. These terms are notated
29%
30.11.2025
zonecfg:web1> add net
09 zonecfg:web1:net> set address=192.168.1.40/24
10 zonecfg:web1:net> set physical=e1000g1
11 zonecfg:web1:net> set defrouter=192.168.1.254
12 zonecfg:web1:net> end
13 zonecfg:web1
28%
17.02.2015
5420 Octa
Quad ARM Cortex-A15 (32KB instruction/32KB data/2MB L2) @1.8GHz, Quad-core ARM Cortex-A7 (32KB/32KB/512KB) @1.3GHz
Mali T-628 MP6
3GB LPDDR3e RAM (14.9GBps memory
28%
14.11.2013
/devices/system/edac/mc/mc0/csrow0/size_mb
8192
login2$ more /sys/devices/system/edac/mc/mc0/csrow0/ue_count
0
Some attribute files in /sys/devices/system/edac/mc/mc0/ can be very useful (Listing 6). As with the csrow
28%
14.08.2017
:31 FS_scan.csv
$ gzip -9 FS_scan.csv
$ ls -lsah FS_scan.csv.gz
268K -rw-r--r-- 1 laytonjb laytonjb 261K 2014-06-09 20:31 FS_scan.csv.gz
The original file is 3.2MB, but after using gzip with the -9
28%
17.09.2013
reset_counters 0 size_mb
0 ce_noinfo_count 0 csrow2 0 csrow5 0 device 0 sdram_scrub_rate 0 ue_count
0 csrow0 0 csrow3 0 csrow6 0 mc_name 0 seconds_since_reset 0 ue_noinfo_count
Notice that this system
28%
14.06.2017
-rw-r--r-- 1 laytonjb laytonjb 261K 2014-06-09 20:31 FS_scan.csv.gz
The original file is 3.2MB, but after using gzip
with the -9
option (i.e., maximum compression), the resulting file is 268KB. The .gz
28%
31.10.2025
of important features). All of the NAS devices in our lab used Intel processors and supported popular RAID levels, at least 1 and 5; the better devices also offered a dual-parity variant like RAID 6. (See
28%
30.11.2025
were run on a virtual system (using ESX as the hypervisor) with fixed reservations for CPU and memory. To be more precise, I used a virtual CPU running at 1.5GHz and with 512MB of RAM in the virtual
