>>> On Tue, 1 Nov 2005 08:22:52 -0500, [EMAIL PROTECTED] said:
[ ... ]
JBorn> /dev/sda1 type ext3
JBorn> /dev/sda2 type ext3
JBorn> /dev/sda3 type swap
JBorn> /dev/sda4 type extended
JBorn> /dev/sda5 free
That looks good.
JBorn> In the background I keep getting the following messages
JBorn> while running qtparted:
JBorn> Error: Filesystem was not cleanly unmounted! You should
JBorn> e2fsck. Modifying an unclean filesystem could cause
JBorn> severe corruption. Error: Could not detect file system.
Both are fine -- unchecked filesystems will be mounted ro, and
probably some of those partitions ('sda5') don't have a
filesystem in them.
But 'qtparted' is complaining here as to «not cleanly unmounted»
simply because '/dev/sda[12]' are most likely _mounted_ as you
are running it on an active system. This is usually safe as long
as you don't mess around with those moujnted partition.
JBorn> Should I be running some sort of file system check
JBorn> weekly?
Well, many file systems have a mount count/interval, and will
run 'fsck' every now and then automatically.
JBorn> I believe I want to create a folder /video or /var/video
JBorn> before I use mkfs.jfs. What is the proper location for a
JBorn> video directory?
That all depends on which naming conventions you like. A file
tree is a classification mechanism for files, and how people
like to classify files is mostly a personal preference.
I personally give proper names to all my filesystems and and
mount them all under '/v' (my own convention), so my file trees
are called something "/v/sugar" "/v/salt" (or whatever other
naming scheme one likes) ; the FSSTND usually recommends
'/media' as the mount point directory, and many distributionas
then use the partition name as the mountpoint name, resulting in
'/media/sda5'.
Then it is easy to use those mount point names directly or to
''graft'' them onto the filesystem tree at any point using
symbolic links or 'mount --bind'.
The reason I prefer proper names for filesystems is that in that
way I can move them around if needed without changing mount
point name; it would be terribly confusing I think if one moved
the contents of '/dev/sda5' to say '/dev/hdd6' and then mounted
'/dev/hdd6' as '/media/sda5' for backwards compatibility. Anyhow
often one would not want to use mountpoint paths directly, but
use symbolic links or 'mount --bind'.
JBorn> and do I create this before running mkfs.jfs?
Just create a directory.
JBorn> Now I want /dev/sda5 to be formatted with jfs what is the
JBorn> mkfs.jfs to run?
Well 'jfs_mkfs /dev/sda5', or 'js_mkfs -L NAME /dev/sda5' if you
want to give the filesystem a name.
JBorn> Where does mount/umount come into the picture?
As to this, it would be somewhat useful to read a discussion of
how UNIX/POSIX/Linux systems handle partitions, filesystems and
mounting.
There are very many introductory tutorials and HOWTOs on disc
handling under UNIX/POSIX/Linux, often as chapters in system
administration books/tutorials.
This one seems rather appropriate:
http://WWW.TLDP.org/LDP/Linux-Filesystem-Hierarchy/html/Linux-Filesystem-Hierarchy.html
JBorn> Since this is a video partition I want to make sure I can
JBorn> add more drives later and just add space to this logical
JBorn> volume?
It is too late (except for some hard and hazardous work) to add
a volume manager underneath.
This is not too bad as I think that except in very very few
cases logical volume managers are largely pointless, because
under UNIX like systems one deals with file trees, and volumes
are just slightly annoying containers for those.
The UNIX like naming trees are/can be almost totally independent
of how the tree is partitioned into volumes, thanks to things
like symbolic links or the Linux 'mount --bind' extension.
Except in special cases (like the root filesystem, or sometimes
'/var/spool', or FAT32 partitions) one might as well create a
single large partition per disk.
People with a MS Windows mindset often still think in terms of
drive letters and therefore volumes, even if ''mounting'' is a
way similar to UNIX like system has been available for a long
time even under MS Windows.
JBorn> is the /dev/sda4 of type extended a logical volumn?
No, extended partitions are just a hack to add more partitions
than the original partition table design allowed.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
