SmartFileSystem 1.290 issue

[samo79]

SmartFileSystem DH1: (sii3114ide.device, Unit 0)

createbnode:findbnode() say key 1394127 already exists

This is the error i got using MUI OWB and even Reaction OWB since the installation of the Update 5 over an old Update 4 install that used the old version of the same FileSystem ...

Can i revert to the old SmartFileSystem using Update 5 ?

[thomasrapp]

I am sure you can revert to an older version of SFS. But it does not matter. The file system structure is corrupted. You need to backup / format / restore anyway.

[saimo]

I am sure you can revert to an older version of SFS.

It is not safe.

[samo79]

Mmm ok, so (rethorical question) if still not safe to revert why the new version of the filesystem is incompatible or similar with old partitions formatted with the same (old) version of SFS ?

If i knew it i would have create a proper backup before .. but now it's not so easy and to be honest a bit annoying ..

[ssolie]

Mmm ok, so (rethorical question) if still not safe to revert why the new version of the filesystem is incompatible or similar with old partitions formatted with the same (old) version of SFS ?

It's not incompatible. You are assuming it is because you are having some issue.

[samo79]

Indeed you are right, i used an erroneous term, but problem still with all my old partitions except SYS: (this because i install OS4.1 Update 1 from scratch there and then all the other updates one by one)

But the partitions formatted with the old SmartFileSystem 1.289 still have issues with Update 5, for example on each start MUI OWB will require a font regeneration of the characters even if all settings was ok, from time to time i got this damn createbnode:findbnode() error and so on (--> random strange behaviours) ..

Mmm format ..

[tonyw]

...from time to time i got this damn createbnode:findbnode() error and so on...

It sounds as though you are getting errors on your hard drive, could be the drive dying or cable/hardware problems. In either case, I suggest you replace the drive and all its contents as soon as you can.

It is not a software problem, otherwise others would have the same problem, and no one else does.

[thomasrapp]

It sounds as though you are getting errors on your hard drive, could be the drive dying or cable/hardware problems.

No, physical problems would look differently. This is a logical problem of the file system structure.

I suggest you replace the drive and all its contents as soon as you can.

This surely is overkill, but it forces him to create new partitions and format them all, so it also solves his problem.

[tonyw]

...This is a logical problem of the file system structure....

Of course it is. Perhaps I didn't express myself clearly. I was trying to say that his filesystem corruptions have been caused by the errors, probably drive or hardware errors.

[thomasrapp]

I don't think so. SFS presents physical errors in error requesters. If no such requester appeared in the past, then no physical error happened.

Also if the drive had problems accessing its data one would clearly recognise it by long delays or noticable head movements or click noises.