Sponsored Content
Top Forums UNIX for Advanced & Expert Users A file system visible for solaris and windows? Post 302406469 by Dann-E on Tuesday 23rd of March 2010 04:25:33 AM
Old 03-23-2010
Question

I never heard of NTFS3G before, I will study it. Anyways, my solaris machine doesn't want to read any usb device I plug: external hard disks, pendrives, etc. I formatted all of them in FAT/FAT32 and if i run the command "Iostat -En", I get illegal requests and soft errors.

I will try to use another filesystem for the usb devices, though if any of you have any better ideas, please share them.

I will write back with my results.

Regards
 

9 More Discussions You Might Find Interesting

1. Linux

Please help me, about the file sharing with windows system

Did anybody can teach me how to set the premission in the samba server? How to i set the premission in one folder but two access right. With one folder but the user access rights is diffirent. One user can full access the folder, and another one user only read only. thx for helping... (1 Reply)
Discussion started by: cloudlor
1 Replies

2. Solaris

How to Install Solaris 10 on top of Windows system

Hi Guru's, Since Iam learning Solaris 10 and want to instal it on to my computer in which 'Windows' is already installed. Also many other applications including Oracle, Java etc,. were also installed associated with Windows. Now how can I install Solaris 10 on my system with out affecting my... (4 Replies)
Discussion started by: Lokesha
4 Replies

3. Linux

UNMOUNT a windows file system

Hi, I try to unmount : smbumount /mnt/directory But I receive : Could not umount /mnt/directory: Device or resource busy Any idea ? Many thanks. (4 Replies)
Discussion started by: big123456
4 Replies

4. Solaris

Junk characters in file not in Solaris, but visible in linux

Hello All, I have a DOS file which I run a DOS 2 UNIX utility on. When run from Solaris, I can view the file perfectly. But, when run from linux, I see a bunch of junk(^@) at the beginning of every line in the file. Does anyone know the cause of this? COMMAND TO CONVERT: tr -d '\015\032'... (7 Replies)
Discussion started by: vada010
7 Replies

5. Solaris

Viewing Solaris File System From Windows Client Using Lanman

Hi I currently have a Windows mapped network drive on a PC which is connected to the network. Also on the network is a Solaris box running Solaris 8 which I can view (root file system) from the Windows PC. The mapped network syntax is sharename\\server name. When I select this mapped drive on... (3 Replies)
Discussion started by: jamba1
3 Replies

6. Solaris

Windows network share visible to Solaris 9 host and vice versa

Hi, I have a Windows server running WinSVR 2008R2 with a network share configured \\hostname\JSS_Share I would like to be able to mount this share on a Solaris host running Solaris 9. I would also like to mount a directory on the Solaris host and make it visible to the Windows server. The idea... (1 Reply)
Discussion started by: jamba1
1 Replies

7. Shell Programming and Scripting

Asking user for input file location using a .sh file in windows system

Hi all, I am creating a .sh file in windows environment using notepad. i need a code which i can write in this .sh file so that it asks me for an input file stored anywhere in my C drive of my windows computer. Please help me out with this. (1 Reply)
Discussion started by: bansalpankaj88
1 Replies

8. HP-UX

how to mount a file system from a solaris server into an hp-ux system

Hi all I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge. The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data. Any help will be appreciated FR (2 Replies)
Discussion started by: fretagi
2 Replies

9. UNIX for Dummies Questions & Answers

Ext2 file system from windows

Hi all, I have some problem with the ext2 file system format. In particolar, I have a unix based system full backup, which is a .iso file. In order to create a bootable usb, i have to format the USB with ext2 FS, and then I have to mount that image on it. The problem is that, I need to it... (3 Replies)
Discussion started by: Mr. Piros
3 Replies
MKFS.FAT(8)                                                   System Manager's Manual                                                  MKFS.FAT(8)

NAME
mkfs.fat - create an MS-DOS filesystem under Linux SYNOPSIS
mkfs.fat [OPTIONS] DEVICE [BLOCK-COUNT] DESCRIPTION
mkfs.fat is used to create an MS-DOS filesystem under Linux on a device (usually a disk partition). DEVICE is the special file correspond- ing to the device (e.g. /dev/sdXX). BLOCK-COUNT is the number of blocks on the device. If omitted, mkfs.fat automatically determines the filesystem size. OPTIONS
-a Normally, for any filesystem except very small ones, mkfs.fat will align all the data structures to cluster size, to make sure that as long as the partition is properly aligned, so will all the data structures in the filesystem. This option disables alignment; this may provide a handful of additional clusters of storage at the expense of a significant performance degradation on RAIDs, flash media or large-sector hard disks. -A Use Atari variation of the MS-DOS filesystem. This is default if mkfs.fat is run on an Atari, then this option turns off Atari format. There are some differences when using Atari format: If not directed otherwise by the user, mkfs.fat will always use 2 sectors per clus- ter, since GEMDOS doesn't like other values very much. It will also obey the maximum number of sectors GEMDOS can handle. Larger filesystems are managed by raising the logical sector size. Under Atari format, an Atari-compatible serial number for the filesystem is generated, and a 12 bit FAT is used only for filesystems that have one of the usual floppy sizes (720k, 1.2M, 1.44M, 2.88M), a 16 bit FAT otherwise. This can be overridden with the -F option. Some PC-specific boot sector fields aren't written, and a boot message (option -m) is ignored. -b SECTOR-OF-BACKUP Selects the location of the backup boot sector for FAT32. Default depends on number of reserved sectors, but usually is sector 6. The backup must be within the range of reserved sectors. -c Check the device for bad blocks before creating the filesystem. -C Create the file given as DEVICE on the command line, and write the to-be-created filesystem to it. This can be used to create the new filesystem in a file instead of on a real device, and to avoid using dd in advance to create a file of appropriate size. With this option, the BLOCK-COUNT must be given, because otherwise the intended size of the filesystem wouldn't be known. The file created is a sparse file, which actually only contains the meta-data areas (boot sector, FATs, and root directory). The data portions won't be stored on the disk, but the file nevertheless will have the correct size. The resulting file can be copied later to a floppy disk or other device, or mounted through a loop device. -D DRIVE-NUMBER Specify the BIOS drive number to be stored in the FAT boot sector. This value is usually 0x80 for hard disks and 0x00 for floppy devices or partitions to be used for floppy emulation. -f NUMBER-OF-FATS Specify the number of file allocation tables in the filesystem. The default is 2. -F FAT-SIZE Specifies the type of file allocation tables used (12, 16 or 32 bit). If nothing is specified, mkfs.fat will automatically select between 12, 16 and 32 bit, whatever fits better for the filesystem size. -h NUMBER-OF-HIDDEN-SECTORS Select the number of hidden sectors in the volume. Apparently some digital cameras get indigestion if you feed them a CF card without such hidden sectors, this option allows you to satisfy them. -i VOLUME-ID Sets the volume ID of the newly created filesystem; VOLUME-ID is a 32-bit hexadecimal number (for example, 2e24ec82). The default is a number which depends on the filesystem creation time. -I It is typical for fixed disk devices to be partitioned so, by default, you are not permitted to create a filesystem across the entire device. mkfs.fat will complain and tell you that it refuses to work. This is different when using MO disks. One doesn't always need partitions on MO disks. The filesystem can go directly to the whole disk. Under other OSes this is known as the 'superfloppy' format. This switch will force mkfs.fat to work properly. -l FILENAME Read the bad blocks list from FILENAME. -m MESSAGE-FILE Sets the message the user receives on attempts to boot this filesystem without having properly installed an operating system. The mes- sage file must not exceed 418 bytes once line feeds have been converted to carriage return-line feed combinations, and tabs have been expanded. If the filename is a hyphen (-), the text is taken from standard input. -M FAT-MEDIA-TYPE Specify the media type to be stored in the FAT boot sector. This value is usually 0xF8 for hard disks and is 0xF0 or a value from 0xF9 to 0xFF for floppies or partitions to be used for floppy emulation. -n VOLUME-NAME Sets the volume name (label) of the filesystem. The volume name can be up to 11 characters long. The default is no label. -r ROOT-DIR-ENTRIES Select the number of entries available in the root directory. The default is 112 or 224 for floppies and 512 for hard disks. -R NUMBER-OF-RESERVED-SECTORS Select the number of reserved sectors. With FAT32 format at least 2 reserved sectors are needed, the default is 32. Otherwise the default is 1 (only the boot sector). -s SECTORS-PER-CLUSTER Specify the number of disk sectors per cluster. Must be a power of 2, i.e. 1, 2, 4, 8, ... 128. -S LOGICAL-SECTOR-SIZE Specify the number of bytes per logical sector. Must be a power of 2 and greater than or equal to 512, i.e. 512, 1024, 2048, 4096, 8192, 16384, or 32768. Values larger than 4096 are not conforming to the FAT file system specification and may not work everywhere. -v Verbose execution. --invariant Use constants for normally randomly generated or time based data such as volume ID and creation time. Multiple runs of mkfs.fat on the same device create identical results with this option. Its main purpose is testing mkfs.fat. --help Display option summary and exit. BUGS
mkfs.fat can not create boot-able filesystems. This isn't as easy as you might think at first glance for various reasons and has been dis- cussed a lot already. mkfs.fat simply will not support it ;) SEE ALSO
fatlabel(8) fsck.fat(8) HOMEPAGE
The home for the dosfstools project is its GitHub project page <https://github.com/dosfstools/dosfstools>. AUTHORS
dosfstools were written by Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>, Roman Hodek <Roman.Hodek@informatik.uni-erlangen.de>, and others. The current maintainer is Andreas Bombe <aeb@debian.org>. dosfstools 4.1 2016-01-25 MKFS.FAT(8)
All times are GMT -4. The time now is 10:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy