On Sun, Apr 04, 2004 at 12:12:00AM -0500, Marvin Stodolsky wrote:
> Thanks all
>
> After turning off the journal with
> tune2fs -O ^has_journal /dev/sda2
> e2fsck reported bad superblocks
...all of them? You can specify alternative superblocks with the -b
option; there are usually several.
--
Thanks all
After turning off the journal with
tune2fs -O ^has_journal /dev/sda2
e2fsck reported bad superblocks
Fortunately, all important Data is copied elsewhere,
So I'll just remake the partition and copy over Debian from this laptop.
Incidentally, there are now available palm sized inclosur
Marvin Stodolsky <[EMAIL PROTECTED]> writes:
> How could I disable the ext3 Journal, so that the file system could be
> more directly FSCKed?
Have you tried mounting them as ext2? It's an outside shot if it
wasn't cleanly unmounted last time but worth a try.
--
Paul Johnson
<[EMAIL PROTECTED]>
Marvin Stodolsky wrote:
> There is a faulty ext3 journal on my Debian desktop system (currently
> on laptop), blocking booting or e2fsck.
> I have an alternate RedHat partition for developement purpuses.
> When I try to fsck the Debian /dev/sda2 therefrom,
> there is a complaint about the Journ
On Sat, Apr 03, 2004 at 03:00:53PM -0500, Marvin Stodolsky wrote:
> There is a faulty ext3 journal on my Debian desktop system (currently
> on laptop),
> blocking booting or e2fsck.
> The precipating event may have been the copying of a tarball to /root/
> which exceeded Root's reserve space.
>
Marvin Stodolsky wrote:
There is a faulty ext3 journal on my Debian desktop system (currently
on laptop),
blocking booting or e2fsck.
The precipating event may have been the copying of a tarball to /root/
which exceeded Root's reserve space.
The shut down appeared normal, but the reboot failed.
There is a faulty ext3 journal on my Debian desktop system (currently
on laptop),
blocking booting or e2fsck.
The precipating event may have been the copying of a tarball to /root/
which exceeded Root's reserve space.
The shut down appeared normal, but the reboot failed.
I have an alternate Red
I just noticed that one of my hard drives was no longer mounting. When
looking through the output of dmesg, I saw the following output
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,68), internal journal
EXT3-fs: mounted filesystem with ordered data m
8 matches
Mail list logo