Sponsored Content
Full Discussion: Mount USB stick...
Special Forums Hardware Filesystems, Disks and Memory Mount USB stick... Post 302342056 by Jucydee on Friday 7th of August 2009 09:59:54 AM
Old 08-07-2009
You seem to ahve forgotten a space

Quote:
Mount -t vfat /dev/sdc1/usbstick
Try this;

Mount -t vfat /dev/sdc1 /usbstick
 

10 More Discussions You Might Find Interesting

1. Linux

bootable USB Stick || Fedora 8

Hello Everybody I am planning to install Fedora core 8 on an extra PC I have; what I wanna do is to boot from a USB stick then install Fedora from an ISO image I already have via FTP. Could any one tell me how to create bootable USB Stick for Fedora as I already found how to install from FTP... (0 Replies)
Discussion started by: ahmed_nasr2001
0 Replies

2. UNIX for Dummies Questions & Answers

Aix usb stick

I have a P-Series Machine running AIX 5.3, it has a USB Port on the front of the server, can I use a USB Stick on AIX platforms?? if so how..:rolleyes: (2 Replies)
Discussion started by: BEVAN
2 Replies

3. BSD

Detecting usb stick in freebsd

I inserted a 8GB usb stick in a number of machine with FreeBSD 7.1, but the medium was not detected: $ dmesg | grep MB usable memory = 4263022592 (4065 MB) avail memory = 4082540544 (3893 MB) pci0: <serial bus, SMBus> at device 31.3 (no driver attached) ad0: 238475MB <WDC WD2500BEVT-00ZCT0... (6 Replies)
Discussion started by: figaro
6 Replies

4. BSD

Mounting a USB stick in FreeBSD

When mounting a USB stick or pen drive on a FreeBSD machine I always issue the following command: mount -t msdosfs /dev/da0s1 /mnt Something I have always wondered is what the option msdosfs stands for and more importantly, why it is necessary. (7 Replies)
Discussion started by: figaro
7 Replies

5. Shell Programming and Scripting

1 usb stick -> 2 mounted devices

Hello, i am using a solaris thinclient that tries to connecting to a terminalserver. (RDP) Everything works fine, but the usb redirection. If i put in a usb stick i always get 2 usb-drives mounted. If i look in /tmp/SUNWut/mnt/<name of the host> i see 2 devices. One with the name of the... (2 Replies)
Discussion started by: anarcy
2 Replies

6. Ubuntu

Ubuntu on USB stick?

Hey Guys I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Discussion started by: rbansal2
3 Replies

7. SCO

Mount USB stick

hi Howto mount an USB stick under SCO 5.0.7? BTW ist it possible to mount USB stick in the command line using 'tools' at the Boot: prompt from OpenServer Release 5.0.7 installation CD? (1 Reply)
Discussion started by: ccc
1 Replies

8. Ubuntu

Installing UBUNTU on USB stick

I'd like to install the OS on my stick. I would like to be able to save my works there and install apps or customize the OS. What can I do Ps. At home I use an iMac, but in the school where I work there are only PC... Ty (2 Replies)
Discussion started by: Fabio_Puricelli
2 Replies

9. SCO

How to use USB Stick in UNIXware?

I am trying to use a USB (Pen?) drive on Unixware 7.1.4. The USB stick is in the machine and the machine recognises it when I enter usbprobe as follows: Path - Address Description ----------------------------- +++++++ BUS #2 0 - 1 - HUB "UHCI Root Hub" 1 - 2 - HID "Chicony Wireless Device"... (1 Reply)
Discussion started by: BernP
1 Replies

10. BSD

Bootable usb-stick, need help, sos

I would probably set all my rubber points here to get some real help for creating a boot device on a usb-stick. There is no CD-drive on this machine, thats why I need to use a usb-stick. And scrumming in a CD-drive to fuddle around in the fstab or something like that is out of reach. My wisdom so... (9 Replies)
Discussion started by: 1in10
9 Replies
PVMOVE(8)						      System Manager's Manual							 PVMOVE(8)

NAME
pvmove - move physical extents SYNOPSIS
pvmove [--abort] [--alloc AllocationPolicy] [-b|--background] [-d|--debug] [-h|--help] [-i|--interval Seconds] [--noudevsync] [-v|--ver- bose] [-n|--name LogicalVolume] [SourcePhysicalVolume[:PE[-PE]...] [DestinationPhysicalVolume[:PE[-PE]...]...]] DESCRIPTION
pvmove allows you to move the allocated physical extents (PEs) on SourcePhysicalVolume to one or more other physical volumes (PVs). You can optionally specify a source LogicalVolume in which case only extents used by that LV will be moved to free (or specified) extents on DestinationPhysicalVolume(s). If no DestinationPhysicalVolume is specified, the normal allocation rules for the Volume Group are used. If pvmove gets interrupted for any reason (e.g. the machine crashes) then run pvmove again without any PhysicalVolume arguments to restart any moves that were in progress from the last checkpoint. Alternatively use pvmove --abort at any time to abort them at the last check- point. You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will ignore any Logical Volumes already in the process of being changed, so some data might not get moved. pvmove works as follows: 1. A temporary 'pvmove' Logical Volume is created to store details of all the data movements required. 2. Every Logical Volume in the Volume Group is searched for contiguous data that need moving according to the command line arguments. For each piece of data found, a new segment is added to the end of the pvmove LV. This segment takes the form of a temporary mirror to copy the data from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in the pvmove LV instead of accessing the data directly. 3. The Volume Group metadata is updated on disk. 4. The first segment of the pvmove Logical Volume is activated and starts to mirror the first part of the data. Only one segment is mir- rored at once as this is usually more efficient. 5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it breaks that mirror so that only the new location for that data gets used and writes a checkpoint into the Volume Group metadata on disk. Then it activates the mirror for the next segment of the pvmove LV. 6. When there are no more segments left to be mirrored, the temporary Logical Volume is removed and the Volume Group metadata is updated so that the Logical Volumes reflect the new data locations. Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using vgconvert(8). N.B. The moving of mirrors, snapshots and their origins is not yet supported. OPTIONS
--abort Abort any moves in progress. --noudevsync Disable udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible udev processing in the background. You should only use this if udev is not running or has rules that ignore the devices LVM2 cre- ates. -b, --background Run the daemon in the background. -i, --interval Seconds Report progress as a percentage at regular intervals. -n, --name LogicalVolume Move only the extents belonging to LogicalVolume from SourcePhysicalVolume instead of all allocated extents to the destination phys- ical volume(s). EXAMPLES
To move all Physical Extents that are used by simple Logical Volumes on /dev/sdb1 to free Physical Extents elsewhere in the Volume Group use: pvmove /dev/sdb1 Any mirrors, snapshots and their origins are left unchanged. Additionally, a specific destination device /dev/sdc1 can be specified like this: pvmove /dev/sdb1 /dev/sdc1 To perform the action only on extents belonging to the single Logical Volume lvol1 do this: pvmove -n lvol1 /dev/sdb1 /dev/sdc1 Rather than moving the contents of the entire device, it is possible to move a range of Physical Extents - for example numbers 1000 to 1999 inclusive on /dev/sdb1 - like this: pvmove /dev/sdb1:1000-1999 To move a range of Physical Extents to a specific location (which must have sufficent free extents) use the form: pvmove /dev/sdb1:1000-1999 /dev/sdc1 or pvmove /dev/sdb1:1000-1999 /dev/sdc1:0-999 If the source and destination are on the same disk, the anywhere allocation policy would be needed, like this: pvmove --alloc anywhere /dev/sdb1:1000-1999 /dev/sdb1:0-999 The part of a specific Logical Volume present within in a range of Physical Extents can also be picked out and moved, like this: pvmove -n lvol1 /dev/sdb1:1000-1999 /dev/sdc1 SEE ALSO
lvm(8), vgconvert(8) pvs(8) Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) PVMOVE(8)
All times are GMT -4. The time now is 01:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy