linux-os (Dick Johnson) wrote:
What is it that you are attempting to do?
Fix my filesystem.
Prevent this situation from happening for others, if at all possible.
First you show us some text obtained while attempting
to run fsck on the loop device,
claiming that this was obtained from a 1TB file-system that
was destroyed by Linux. Then you spend several days telling us
that linux is no good. Enough is enough.
That was never really my point, apologies if it came across that way.
If you had a 1TB file-system and you knew anything about Unix or
Linux, it would have been fixed by now
What? Uh.
Well, whatever.
-- and BTW, samba can't
destroy a file-system, no matter how many files were open.
Never claimed that it did.
The worse possible situation is that files, open for write, may
not be completely written and this only for files that were
being created or extended. You still have the original file-data
and all the rest of the files on your file system.
Well, it doesn't mount, so they're kind of irretrievable right now.
Another point... ext3 is a journaled file-system. Even when
forced off by hitting the reset switch, ext3 will quietly
announce "recovering from journal" and mount just fine.
Obviously that's not true.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
