From: David van Hoose <david.vanhoose@comcast.net>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Helge Hafting <helge.hafting@hist.no>,
John Richard Moser <nigelenki@comcast.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Collapse ext2 and 3 please
Date: Fri, 25 Jun 2004 08:18:18 -0400 [thread overview]
Message-ID: <40DC180A.40204@comcast.net> (raw)
In-Reply-To: <1088165426.16286.67.camel@imp.csi.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Anton Altaparmakov wrote:
> On Fri, 2004-06-25 at 13:05, David van Hoose wrote:
>
>>All ext3 partitions are labeled as ext3. It still panics.
>
>
> Could you show your /etc/fstab? (Only the root fs entry is of
> interest.)
>
> And the output of: tune2fs -l /dev/hda1 | grep -i journal
>
> You need to replace /dev/hda1 with your actual boot device...
>
> Best regards,
>
> Anton
[root@bahamut root]# /sbin/tune2fs -l /dev/sda2 | grep -i journal
Filesystem features: has_journal filetype needs_recovery sparse_super
Journal inode: 8
Journal backup: inode blocks
fstab is attached.
I have separate partitions for / and /boot, however, the outputs are all
the same.
Regards,
David
[-- Attachment #2: fstab --]
[-- Type: text/plain, Size: 816 bytes --]
/dev/sda2 / ext3 defaults 1 1
/dev/sda1 /boot ext3 defaults 1 2
/dev/sda5 swap swap defaults 0 0
/dev/sda6 /home ext3 defaults 1 3
/dev/sda7 /mnt/data auto sync,uid=root,gid=shared,umask=007 1 3
/dev/sda8 /mnt/mp3s auto sync,uid=root,gid=shared,umask=007 1 3
/dev/hda1 /mnt/backup ext3 defaults 1 4
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
next prev parent reply other threads:[~2004-06-25 12:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:14 Collapse ext2 and 3 please John Richard Moser
2004-06-25 9:16 ` Helge Hafting
2004-06-25 11:30 ` David van Hoose
2004-06-25 11:41 ` Christoph Hellwig
2004-06-25 11:50 ` David van Hoose
2004-06-25 12:01 ` Matthew Garrett
[not found] ` <1088165028.16286.59.camel@imp.csi.cam.ac.uk>
2004-06-25 12:05 ` David van Hoose
2004-06-25 12:13 ` Matthew Garrett
[not found] ` <1088165426.16286.67.camel@imp.csi.cam.ac.uk>
2004-06-25 12:18 ` David van Hoose [this message]
2004-06-25 13:03 ` Tigran Aivazian
2004-06-25 12:40 ` David van Hoose
2004-06-25 14:03 ` Rik van Riel
2004-06-25 12:10 ` Christoph Hellwig
2004-06-25 12:15 ` David van Hoose
2004-06-25 12:26 ` Richard B. Johnson
2004-06-25 12:48 ` Philip R. Auld
2004-06-25 12:53 ` David van Hoose
2004-06-25 13:39 ` Tigran Aivazian
2004-06-25 18:55 ` David van Hoose
2004-06-25 22:26 ` John Richard Moser
2004-06-25 12:25 ` Sean Neakums
2004-06-25 18:01 ` Timothy Miller
2004-06-25 18:04 ` Sean Neakums
2004-06-25 18:41 ` Timothy Miller
2004-06-25 20:52 ` R. J. Wysocki
2004-06-25 20:50 ` Sean Neakums
2004-06-25 21:36 ` R. J. Wysocki
2004-06-25 22:00 ` Andrew Morton
2004-06-25 23:48 ` John Richard Moser
[not found] <2aZfF-3es-5@gated-at.bofh.it>
[not found] ` <2b45V-6tl-39@gated-at.bofh.it>
2004-06-25 22:28 ` Pascal Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40DC180A.40204@comcast.net \
--to=david.vanhoose@comcast.net \
--cc=aia21@cam.ac.uk \
--cc=hch@infradead.org \
--cc=helge.hafting@hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox