Re: [Evms-devel] Reg: Making File Systems

[Chris B. <ch...@po...>]

On 26 Nov 2004, at 18:23, Chris Birkinshaw wrote:

>
> On 26 Nov 2004, at 15:29, Kevin Corry wrote:
>
>> Hi Susmitha,
>>
>> On Thursday 25 November 2004 04:10, susmitha wrote:
>>> While making FileSystems JFS and NTFS on a volume i am getting error 
>>> as
>>> ----------
>>> For JFS
>>> ----------
>>> Engine: FSIM plug-in JFS returned error code 255 when called to mkfs 
>>> on
>>> volume /dev/evms/md/md0
>>>
>>> Unknown error 255
>>> ----------
>>> For NTFS
>>> ----------
>>> Engine: FSIM plug-in NTFS returned error code 2 when called to mkfs 
>>> on
>>> volume /dev/evms/md/md0
>>>
>>> The specified item could not be found.
>>>
>>> I am sending log file also which runned in debug mode.
>>
>> From the log you included, it doesn't look like you have the NTFS of 
>> JFS
>> utilities installed. It looks like it tried running "mkntfs -V" and
>> "mkfs.jfs" but got back "No such file or directory" errors. If you 
>> want to
>> use the various FSIMs in EVMS, make sure you have the appropriate 
>> filesystem
>> tools packages installed on your system. In this case, see if you 
>> have the
>> ntfsprogs and jfsutils packages installed.
>>
>>> One more doubt if i made filesystem with ext2 or ext3 with enabling
>>> journal can I know what is exact filesystem other that Ext2/3.
>>>
>>> While querying for volumes I am getting as Ext2/3 not as Ext2 or 
>>> Ext3.
>>> Can any one please help me.
>>
>> It doesn't look like EVMS has a way to provide this information. 
>> However, you
>> can use tune2fs to see if a volume with an ext2/3 filesystem has a 
>> journal or
>> not. Run "tune2fs -l /dev/evms/md/md0", then look for the line 
>> beginning with
>> "Filesystem features" and see if it contains "has_journal" or not.
>>
>
> Just ran the tune2fs command on it and got this:
>
> tune2fs -l /dev/evms/md/md2
>
> tune2fs 1.32 (09-Nov-2002)
> Filesystem volume name:   <none>
> Last mounted on:          <not available>
> Filesystem UUID:          7c322fc3-5fc0-476f-8398-771bfa68869a
> Filesystem magic number:  0xEF53
> Filesystem revision #:    1 (dynamic)
> Filesystem features:      has_journal filetype needs_recovery 
> sparse_super large_file
> Default mount options:    (none)
> Filesystem state:         clean
> Errors behavior:          Continue
> Filesystem OS type:       Linux
> Inode count:              43974656
> Block count:              87919488
> Reserved block count:     4395974
> Free blocks:              11157630
> Free inodes:              43949850
> First block:              0
> Block size:               4096
> Fragment size:            4096
> Blocks per group:         32768
> Fragments per group:      32768
> Inodes per group:         16384
> Inode blocks per group:   512
> Filesystem created:       Mon Aug 11 16:33:37 2003
> Last mount time:          Wed Nov 24 08:45:44 2004
> Last write time:          Wed Nov 24 08:45:44 2004
> Mount count:              31
> Maximum mount count:      36
> Last checked:             Wed Oct  6 21:53:30 2004
> Check interval:           15552000 (6 months)
> Next check after:         Mon Apr  4 21:53:30 2005
> Reserved blocks uid:      0 (user root)
> Reserved blocks gid:      0 (group root)
> First inode:              11
> Inode size:               128
> Journal UUID:             <none>
> Journal inode:            8
> Journal device:           0x0000
> First orphan inode:       0
>
>

Sorry, replied to wrong thread!