|
|
Sponsored Content
Operating Systems
Solaris
Creating a partition....???
Post 302272495 by bharu_sri on Tuesday 30th of December 2008 07:50:41 PM
12-30-2008
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi,
1) is logical partition the same as physical partition except that one is physical and the other is logical?
2) then it must a one to one ratio? (3 Replies)
Discussion started by: yls177
3 Replies
2. UNIX for Dummies Questions & Answers
Dear Members,
I am using SCO-Unix 5.0.5. I have created 2 logical drives but some of the blocks are overlapped and are now giving warning during startup. I have used fsck to settle the problems but to no avail. Kindly help me to sort out the problem.
Thanks (3 Replies)
Discussion started by: nagendrajaiswal
3 Replies
3. UNIX for Dummies Questions & Answers
I've created a partition with GNU Parted, how do I mount the partition?
The manual information at http://www.gnu.org/software/parted/manual/parted.html is good, but I am sure about how I mount the partition afterwards.
Thanks,
--Todd (1 Reply)
Discussion started by: jtp51
1 Replies
4. Filesystems, Disks and Memory
I have 40GB HD with mepis8, swap, MBR and under flags word boot.
I also have a 160 GB external with a few Linux OS, no swaps, no extended etc. I am total Linux no MS
I would feel more secure by resizing that sda1 partition and creating a /boot partition with the MBR housed there. Is that a... (1 Reply)
Discussion started by: worthamtx
1 Replies
5. UNIX for Advanced & Expert Users
I needed to create a un-formatted partition of X MB on a disk dont want it from GUI but from command line not sure what should be specified for fdisk (4 Replies)
Discussion started by: dinjo_jo
4 Replies
6. Solaris
hi all
while formatting hard disk i am getting following error.
Partition 1 ends at 266338338
It must be between 34 and 143374704.
label error: EFI Labels do not support overlapping partitions
Partition 8 overlaps partition 1.
Warning: error writing EFI.
Label failed.
I have formatted the... (2 Replies)
Discussion started by: nikhil kasar
2 Replies
7. OS X (Apple)
I have a drive full of diagnostic images (ASD), and I also use it for storage, installers, etc. When I plug it in to a booted system, it has to mount every single volume (about 25) which can take some time. I would like to keep all the ASD partitions from mounting when plugged in/at boot. I know... (0 Replies)
Discussion started by: nextyoyoma
0 Replies
8. Linux
Hi,
I have a server booted into sysresccd (mini-linux OS) with 1 40 GB disk attached
I am trying to create a volume group and restore another server into the new one
However, when I try to create a partition for /boot it seems that my VG in LVM is not recognized anymore
These are the... (2 Replies)
Discussion started by: galuzan
2 Replies
9. Red Hat
Hello All,
I have a Red Hat Linux 5.9 Server installed with one hard disk & 2 Partitions created on it as follows,
/boot - Linux Partition & another is
LVM - One VG & under that 5-6 Logical volumes(var,opt,home etc).
Here my requirement is to take out 1GB of space from LVM ( Any logical... (5 Replies)
Discussion started by: gr8_usk
5 Replies
10. Solaris
Hi all,
I am using SPARC Solaris 11.1 with EFI labelled disks.
I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs.
EFI labels use sectors and blocks and I am not sure how exactly it works.
From here I can try and create a... (2 Replies)
Discussion started by: selectstar
2 Replies
LEARN ABOUT DEBIAN
fssync-debug_mode
FSSYNC-DEBUG_MODE(8) AFS Command Reference FSSYNC-DEBUG_MODE(8) NAME
fssync-debug_mode - Changes volume attach mode (FSYNC_VOL_NEEDVOLUME opcode) SYNOPSIS
fssync-debug mode -volumeid <volume ID> [-partition <exact partition name>] [-reason <sync protocol reason code>] [-programtype <program type code>] [-help] fssync-debug mod -v <volume ID> [-pa <exact partition name>] [-r <sync protocol reason code>] [-pr <program type code>] [-h] fssync-debug needvolume -v <volume ID> [-pa <exact partition name>] [-r <sync protocol reason code>] [-pr <program type code>] [-h] fssync-debug n -v <volume ID> [-pa <exact partition name>] [-r <sync protocol reason code>] [-pr <program type code>] [-h] DESCRIPTION
The fssync-debug mode command changes volume attach mode. OPTIONS
-volumeid <volume ID> Specifies the numeric volume ID. Volume names are not permitted. -partition <exact partition name> Specifies the exact partition name (e.g. /vicepa). Abbreviations are not permitted. -reason <sync protocol reason code> Specifies numeric sync protocol reason code. Available codes are listed in OpenAFS source file src/vol/fssync_inline.h. For SYNC_REASON_NONE, use -reason 0. -programtype <program type code> Specifies program type code. Permitted values are fileServer, volumeUtility, salvager, salvageServer, volumeServer and volumeSalvager. PRIVILEGE REQUIRED
The issuer must have write access to the file server. Usually, this means that the issuer must be the local superuser "root" on the file server machine. SEE ALSO
fssync-debug_attach(8), fssync-debug_detach(8), fssync-debug_callback(8), fssync-debug_online(8), fssync-debug_offline(8), fssync-debug_error(8) COPYRIGHT
Copyright 2010 Davor Ocelic <docelic@spinlocksolutions.com> This documentation is covered by the IBM Public License Version 1.0. This man page was written by Davor Ocelic for OpenAFS, based on documentation from Steven Jenkins, Tom Keiser and Simon Wilkinson. OpenAFS 2012-03-26 FSSYNC-DEBUG_MODE(8)