Yup, even with the fsck -f option, the drive is clean.
The windows was connecting via samba (hence windows).
On Sun, Jul 13, 2008 at 7:56 PM, Matija Nalis <mnalis-ml@xxxxxxxxxx> wrote:
On Sun, Jul 13, 2008 at 01:01:27AM +0200, Iskandar Prins wrote:is underlying block device a single hard disk, or maybe a RAID1 or similar ?
> At the moment I'm looking at the filesystem (onto which I made those changed
> last week) , but it seems I'm looking at the filesystem from a month ago (
> june 20th).
I had a similar problem once, which turned out to be RAID1 which was out of
sync (but wrongly thining it is OK!), so sometimes it read "right" data from
one disk, and some times "bad" data from other disk. Solution was to break
the RAID, force fsck it, and recreate the raid afterwards.
you did specify -f to force it, I assume ?
> I did a fsck/e2fsck on the umounted devs and they can't get any cleaner.
--
Opinions above are GNU-copylefted.
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
_______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
