On 05/10/13 17:12, Duaine Hechler wrote:
On 10/04/2013 10:17 PM, Basil Chupin wrote:
On 05/10/13 13:13, Duaine Hechler wrote:
On 10/03/2013 02:04 PM, Duaine Hechler wrote:
On 10/03/2013 07:02 AM, Anton Aylward wrote:
Duaine Hechler said the following on 10/03/2013 01:28 AM:
So bottom line, I guess my question is - what is the best fs + the best file recovery fs ?
Without defining context, "best" is meaningless. What's good for you may not be good for me. Context is everything. Carving on tablets of stone is an adequate response to the way you've posed your question and was good enough for the Greeks and Romans.
You're trolling.
Trolling ........... well ........... if you would drop your eyes down to my sig line - you would see the main context of my drives.
Self employed, small business owner (accounting (Quasar), Firefox, Thunderbird)) (+ household entertainment file server (movies, mp3s, etc) + printer sharing server) (Running from Primary drive and Secondary drive as backup using rsync) (Third small drive with VB running Win 7 - data files being shared to Linux Primary drive)
Is this what you are looking for, to give me a better answer ?
Well ............. I bit the bullet and converted to ext4 !
Is that why I felt the earth move? :-)
BC
Maybe .... Is there a reason I keep seeing disk activity when I'm doing nothing - related to ext4 journaling ?
I am not sure. I remember that I had this "trouble" some years ago and after raising the question here about this managed to trace the "problem" to some process which kept checking to see if there was data waiting to be written to disk. But this was when I was using ext3 (or even possibly Reiserfs - can't remember which). I have been using ext4 for years now and don't see this. One thing you could try is to run e2fsck MANUALLY and *without* using the auto fix option ( -p ) and see if the file system is 'clean'. (I know that fsck is run at every boot but it doesn't do a full check - I learnt this from experience.) To run e2fsck, boot into level #1 then as root: mount -o remount,ro /dev/sdaXX where sdaXX is the / partition and answer the questions - if they appear; if they do appear then let e2fsck do the repairs. I normally remount sdaXX with: mount - remount,rw /dev/sdaXX and then rebooting. Have a look at the man e2fsck to get info re e2fsck if you want to know more. BC -- Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.3-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org