What does this I/O error mean and how to mount it back Post: 302111139

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

553 config error: mail loops back to me (MX problem)

I recieve 553 5.3.4 mail.xxxx.com config error: mail loops back to me (MX problem?) when I try to send email from client . The message reaches the server and dies there I'm using sendmail 8.12.9 on OpenBSD 3.3. I can check mail on client with no problem Thanks for any help

2. SCO

back-up drive : tape error

i have an ibm machine with dds4 drive running sco. i bought new hp dds4 tape for my back-up. the new tapes are not being read by the system, it says tape error, no such device. i've already clean the drive several times but still the same error occur. i've tried to use the same tape on our windows...

3. Shell Programming and Scripting

back reference error

Hi, i am getting this error........ find ./ | sed '/\(*\) \(*\)/\2\1/' Unrecognized command: /\(*\) \(*\)/\2\1/ Any idea??? regards Apoorva Kumar

4. AIX

back to back printing in UNIX

Hi , Can you suggest me how to back to back printing in UNIX? Is there any way? Kindly advise. Regards Vijaya Amirtha Raj

5. IP Networking

Back-to-Back Connection using HBAs

Hi every body, Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber. Note it is direct connection & there is no switches between the servers. I'm concern about using HBA adapters, it is possible or not. Thanks in advance. :)

6. Solaris

how to mount back the slice 7

Hi, i encounter problem during middle progress of mirroring. i trying create a mirror (metainit) to my slice 7. Who's have any experience, can you please help me? i tried create a state database replica "metadb -afc1 /dev/dsk/cxtxdxs7" but at it show it cannot create caused /dev/dsk/cxtxdxs7...

7. Shell Programming and Scripting

Passing error message back to script

I have one script that calls another script during execution. The other script does some processing, then either returns with exit 0 (if successful), or exits with error code numbers (if failed). However, in addition to the error code, I would like for that second script to be able to pass a...

8. Solaris

Mail loops back to me error in /var/adm/message after patching

Hi, I am getting the below messsage in /var/adm/message after patching but sendmail is working after restoring the backup file. sendmail: q4G7U1Cj014774: SYSERR(root): 127.0.0.1 config error: mail loops back to me (MX problem?) sendmail: q4G801cw025824: SYSERR(root): 127.0.0.1 config...

9. Shell Programming and Scripting

sed back reference error

I am trying to change a single line of a special file whose comment character is ! to show a path to the file in the comment. such as: !!HFSS and mcm path: \Signal_Integrity\Package_SI\Section_Models\C4toTrace\28nm\D6HS\SLC_5-2-5\GZ41_ICZ\NSSS\ to a different path and replace the !!HFSS...

LEARN ABOUT FREEBSD

msdosfs

MSDOSFS(5)						      BSD File Formats Manual							MSDOSFS(5)

NAME

     msdosfs -- MS-DOS file system

SYNOPSIS

     options MSDOSFS

DESCRIPTION

     The msdosfs driver will permit the FreeBSD kernel to read and write MS-DOS based file systems.

     The most common usage follows:

	   mount -t msdosfs /dev/ada0sN /mnt

     where N is the partition number and /mnt is a mount point.  Some users tend to create a /dos directory for msdosfs mount points.  This helps
     to keep better track of the file system, and make it more easily accessible.

     It is possible to define an entry in /etc/fstab that looks similar to:

     /dev/ada0sN	     /dos    msdosfs	     rw      0	     0

     This will mount an MS-DOS based partition at the /dos mount point during system boot.  Using /mnt as a permanent mount point is not advised
     as its intention has always been to be a temporary mount point for floppy and ZIP disks.  See hier(7) for more information on FreeBSD direc-
     tory layout.

SEE ALSO

     mount(2), unmount(2), mount(8), mount_msdosfs(8), umount(8)

AUTHORS

     This manual page was written by Tom Rhodes <trhodes@FreeBSD.org>.

BSD
								  October 1, 2013							       BSD