Hello,

since today I get SFS errors during browsing web sites: http://www.sprocki.net/sfs.png
This affects my Cache: partition where IBrowse finds it cache directory although I disabled it in the settings.
What does it mean now? Does SFS try do create a new node and isn't able to do so because of one with the same key is already there? If so, why is SFS not aware of its own nodes, then?
What shall I do now? Reformat the whole partition?

Backup files and format.

And why isn't SFS aware of these nodes?

sorry for bringing this old topic back, but its happening to me now.

after browsing (and dling a file) with ibrowse 2.4 i got a checksum error (my ibrowse cache was a dir at my 2nd partition).
after tried to repair it with sfsdoctor, more then a half of all of the files and dirs from that partition has gone to >nil:...

then i turn off the ibrowse cache - few minutes (and with a downloaded file) later another cheksum error showed up, then the same error as in the first post...

can someone tell me wtf is this?
thx.

be really careful, when talking about salvage of bad sfs partition data... this way, some directories disappeared from my partition without any possibility to be saved... i ofcourse realized that much later. and this happend already two or three times (i'm using sfs for about 6 years now?)

afaik, i can recommend to defragment your partition to avoid some troubles. also try the sfs check to find out, if there are some problems...

bye, MarK.

Never trust any filesystem. Never.

Also make regular backups of important data (have a 2nd HD to make dayly/weekly backups, store important stuff to CD/DVD monthly). Thats the best way to avoid possible trouble.

About SFS: if you got recurring error. Don't do anything with that partition anymore. Copy off data as much as possible (use filer or diropus 4) and then reformat. And copy back.

Thats why it's good to have a smart partition scheme (using whole hd with just 1 or 2 partition is akward in such cases).

thanks for the advices!

i've never had problems with sfs before, until this case...

i thought it was rock solid:)

good to hear that someone had the same file disappears, so it seems my system is not totally wrecked:)

i recover all of the files of the "bad" partition to another with sfsdoctor. but after that i havent formatted the partition just repaired it. should i reformat it?

i have a 80gig had with 4 mos (1 ffs 3 sfs) and 3 linux (ext2 + swap) partitions on it.

oh my.... will sfs be better or safer in the next mos release?

I haven't got such a problems with SFSDoctor ever. When it was in beta stage, it was unable to repair my partitions (two times, if I remember correctly). I drop an e-mail to March and I got fixed version of SFSDoctor the same day.

So I strongly recommend you to inform SFSDoctor author about your problems.

i realized one thing... when 80wired cables are damaged, these sfs errors can appear very often. i have some of these probably broken, because these errors appears usualy when i change something inside the pegasos case... when i realize, that there are these errors, it's usualy enough to shake with these cables, and it's okay then...

best way is to use rounded cables, which are much safer with manipulation...

bye, MarK.

Quote:
In my opinion, it's most definitely NOT okay if you have to shake the cables to make it (not) okay

i ofcourse know... but it's the way, i can make it working untill i will get better (and more expensive) round cables...

bye, MarK.