All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Singh <manish.singh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Re: Playing with OCFS2
Date: Thu Jan 29 18:19:17 2004	[thread overview]
Message-ID: <20040130001905.GC10332@ca-server1.us.oracle.com> (raw)
In-Reply-To: <50D19C3AC815734C9E19FE4C4F6128A6178026@orsmsx403.jf.intel.com>

On Thu, Jan 29, 2004 at 03:21:58PM -0800, Villalovos, John L wrote:
> I just took the latest version of OCFS2 code from Subversions today.
> 
> I am using a Fedora Core 1 system with all updates applied.
> 
> I am using a Firewire Maxtor drive to put it on.  Currently only testing
> with one computer and one drive.
> 
> I was able to build the OCFS2 and OCFS-TOOLS components with no
> problems.
> 
> I copied the ocfs2.o module to my local /lib/modules... Directory.
> 
> I ran:
> 	mkfs.ocfs -F -b 128 -L ocfs-test -m /ocfs /dev/sda1
> 	(not sure why mkfs.ocfs wants to know where the partition will
> be mounted???)
> 
> I ran:
> 	ocfstool and created my /etc/ocfs.conf
> 
> I then ran:
> 	load_ocfs2 and it complained about ip_port_v2 missing.  So I
> created an ip_port_v2 entry with a value of 7002.
> 
> Re-ran:
> 	load_ocfs2 and the driver loaded.
> 
> I then tried to mount the volume:
> 	mount -t ocfs /dev/sda1 /ocfs
> 
> 	waited for awhile and it returned but no drive was mounted :(
> 
> So I'm not sure what I did wrong.
> 
> Any suggestions would be appreciated.

The filesystem type for OCFS2 is "ocfs2", not "ocfs". Not sure why it would
take a long time with "ocfs" though..

Try with "ocfs2" and see what happens.

-Manish

  reply	other threads:[~2004-01-29 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 17:29 [Ocfs2-devel] Playing with OCFS2 Villalovos, John L
2004-01-29 18:19 ` Manish Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-29 18:21 [Ocfs2-devel] " Villalovos, John L

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=20040130001905.GC10332@ca-server1.us.oracle.com \
    --to=manish.singh@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.