search for: wears

Hello! I'm using a CompactFlash as storage device. Since those CF cards only have limited write cycles (CF does wear-levelling by itself, but you don't want to write too many timet so the card) i was wondering by what a factor the journaling of ext3 increases the write accesses to the CompactFlash compared to ext2. Thanks a lot already for your help! Sincerely Chris Braun

Dear friends, I have used R for some time now and have a tricky question about the coxph-function: To sum it up, I am not sure whether I can use coxph in conjunction with missing covariate data in a model with time-variant covariates. The point is: I know how "old" every piece that I oberserve is, but do not have fully historical information about the corresponding covariates. Maybe you

...rite cycles, but not nearly as large as hard drives: http://en.wikipedia.org/wiki/Flash_rom#Limitations . So using Flash in place of RAM, even when high speed isn't important, can wear out the Flash - it will probably wear out even before HDs, which live less long than does RAM. Until the Flash wears out, it is extremely reliable, and techniques for ensuring it doesn't destroy data as it wears out are built into the Flash HW (though it will eventually wear out take data with it). But I'm not talking about using the Flash as RAM, just using it for a low-load persistent store like a HD,...

Hi, I don''t know if it''s already been discussed here, but while thinking about using the OCZ Vertex 2 Pro SSD (which according to spec page has supercaps built in) as a shared slog and L2ARC device it stroke me that this might not be a such a good idea. Because this SSD is MLC based, write cycles are an issue here, though I can''t find any number in their spec. Why do I

I''ve got two recent examples of SSDs. Their pristine state from the manufacturer shows: Device Model: OCZ-VERTEX3 # hexdump -C /dev/sdd 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 1bf2976000 Device Model: OCZ VERTEX PLUS (OCZ VERTEX 2E) # hexdump -C /dev/sdd 00000000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| *

Hi! With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it trimmed: merkaba:~> fstrim -v /boot /boot: 224657408 bytes were trimmed merkaba:~> fstrim -v /boot /boot: 0 bytes were trimmed But BTRFS does not: merkaba:~> fstrim -v / /: 4431613952 bytes were trimmed merkaba:~> fstrim -v / /: 4341846016 bytes were trimmed Is it planned to add this feature to BTRFS

Hi, i try to create a openWRT Samba 4.3 package and stumbled across the fact that samba 4.3 will create those message socks inside the private-dir. That results in creating entries inside /etc/samba/msg.sock. On openWRT /var is a tempFS in ram, so anything there is not a problem regarding nvram and wear leveling. Yet the root uses a jffs2 overlay. So while those message socks have no size, jffs2

I''m looking to try BTRFS on a SSD, and I would like to know what SSD optimizations it applies. Is there a comprehensive list of what ssd mount option does? How are the blocks and metadata arranged? Are there options available comparable to ext2/ext3 to help reduce wear and improve performance? Specifically, on ext2 (journal means more writes, so I don''t use ext3 on SSDs,

On 11/03/16 12:08, Andy Walsh wrote: > Hi, > > i try to create a openWRT Samba 4.3 package and stumbled across the fact > that samba 4.3 will create those message socks inside the private-dir. That > results in creating entries inside /etc/samba/msg.sock. > > On openWRT /var is a tempFS in ram, so anything there is not a problem > regarding nvram and wear leveling. Yet the

Something else that you might want to do is count the number of journal commits that are taking place, via a command like this: perf stat -e jbd2:jbd2_start_commit -a sleep 3600 This will count the number of jbd2 commits are executed in 3600 seconds --- i.e., an hour. If you are running some workload which is constantly calling fsync(2), that will be forcing journal commits, and those turn into

Well, the first day was interesting. We a variety of questions from why do we do this, what's going on with RH, how come this is the first I've heard of you. And hundreds more. The good thing is that we've recieve a very positive response from everyone that visited our booth. Such a positive response that all our CentOS CD's are gone, and most of the cAos CD's are gone, and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, I been using CF cards for almost more then 7 years now with ext file-system without any major problems on ALIX boards. Last year I took 30 other systems in production with ext4 and the CF cards been dropping out pretty fast, it may have been a bad batch but I do want to look at it. I don't think the devices writes a lot of IO (is

On Oct 8, 2014, at 10:28 AM, Jelle de Jong <jelledejong at powercraft.nl> wrote: > Hello everyone, > > I been using CF cards for almost more then 7 years now with ext > file-system without any major problems on ALIX boards. > > Last year I took 30 other systems in production with ext4 and the CF > cards been dropping out pretty fast, it may have been a bad batch but

Rowland penny <rpenny <at> samba.org> writes: > > On 11/03/16 12:08, Andy Walsh wrote: > > Hi, > > > > i try to create a openWRT Samba 4.3 package and stumbled across the fact > > that samba 4.3 will create those message socks inside the private-dir. That > > results in creating entries inside /etc/samba/msg.sock. > > > > On openWRT

Hi We have a number offices accommodating 4-6 people each hence it is very important for PBX to be fanless and silent. We have been looking at using IDE flash disks also called DOM. The performance tests we have done so far satisfy our requirements, however we are concerned with DOM durability. We have installed debian and vanilla asterisk on 1GB DOM. All seems to work fine at the moment however

On Oct 16, 2014, at 10:25 AM, Bodo Thiesen <bothie@gmx.de> wrote: > * Andreas Dilger <adilger@dilger.ca> hat geschrieben: > >> You can see in the ext4 superblock the amount of data that has been >> written to a filesystem over its lifetime: >> >> Note that this number isn't wholly accurate, but rather a guideline. > > Is is more like a

Has anyone installed a high I/O application such as an email server on SSD drives? Was thinking about doing two SSD's in RAID1. It would solve my I/O latency issues but I have heard that SSD's wear out quickly in high I/O situations? Something like each memory location only has X many writes before its done. Just wandering if anyone has tested it and if newer SSD's are better about

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

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > You can see in the ext4 superblock the amount of data that has been > written to a filesystem over its lifetime: > > Note that this number isn't wholly accurate, but rather a guideline. Is is more like a completely bogus value at best: # LANG=C df -h / | grep root /dev/root 3.7T 3.6T 73G 99% / # grep [0-9]

I'm writing a program that will tell me whether I should wear a coat, so I'd like to be able to download daily weather forecasts and daily reports of recent past weather conditions. The NOAA has very promising tabular forecasts (http://forecast.weather.gov/MapClick.php?CityName=Ithaca&state=NY&site=BGM&textField1=42.4422&textField2=-76.5002&e=0&FcstType=digital),