09-06-2009
I wonder if the LUNs are not being unmounted cleanly on reboot. Perhaps some processes were still using them. I also wonder why s2 is being referenced, are you mounting the whole disk?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone have any advice on what print servers to use with Solaris I used to use intel but they dicontinued the model we used. I would just use lpadmin to set them up . Any advice on this would be very helpful. (2 Replies)
Discussion started by: xmildx
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Discussion started by: i2admin
3 Replies
3. Solaris
Hi,
Please can someone recommend me a cheap PCI Network card for Solaris 9 (9/05) for an Intel based PC (x86).
I currently have a US Robotics NIC installed, but Solaris does not recognise it and its been too much hassle to find drivers for it etc, so have decided to purchase another NIC that... (3 Replies)
Discussion started by: wajidc
3 Replies
4. BSD
Hi, I'm new to BSD and would like to create a dual-boot between Solaris Express Community Edition and FreeBSD.
I would just like to know if the Solaris UFS file system can be written to by BSD?
I know that BSD uses UFS2, but I'm hoping that it is backwards compatible with UFS1 provided that... (0 Replies)
Discussion started by: Johnny SSH
0 Replies
5. UNIX for Advanced & Expert Users
Hello,
For a company I have to check if it is possible to migrate there environment from a solaris 8 to solaris 10.
Is there a tool with which I can check if the libraries running now on the 8 are compatible with the 10?
Kind regards (3 Replies)
Discussion started by: chelle007
3 Replies
6. Shell Programming and Scripting
Hi folks
There are about 200 csh scripts (I didn't wrote them). Do all those scripts run with tcsh without modification? Is tcsh 100% compatible with the plain-old csh?
$ which csh
/usr/bin/csh
$ which tcsh
/usr/bin/tcsh
$ uname -a
SunOS purzelse 5.9 Generic_117171-07 sun4u sparc... (2 Replies)
Discussion started by: slashdotweenie
2 Replies
7. Solaris
how do you get start and end sector of a UFS slice? (2 Replies)
Discussion started by: orange47
2 Replies
8. Solaris
i heard some where veritas volume manager wont work on solaris x86. i have installed vmware into my 32bit xp machine. i am planning to learn veritas..
is there an veritas volume manager version compatible with solaris x86 machine? (2 Replies)
Discussion started by: chidori
2 Replies
9. Solaris
I'm prompted to start this thread following my attempt to help on this thread here (see my posts).
I was proposing the OP deep checked a Solaris ufs filesystem using:
# fsck -o full <filesystem node>
however this option does not appear to be valid on Solaris 10.
I've used... (8 Replies)
Discussion started by: hicksd8
8 Replies
10. Solaris
I have a Solaris 10 LDOM installed with UFS and another Solaris 11 LDOM with ZFS. I want to mount a folder on Solaris 10 to Solaris 11. I used the following:
sudo mount -F ufs 10.1.1.44:/export/home/amandeep/workspace /home/amandeep/workspace/mounts/ldom5
and it errors out with:
mount:... (7 Replies)
Discussion started by: amandeepgautam
7 Replies
LEARN ABOUT MOJAVE
fsck_exfat
FSCK_EXFAT(8) BSD System Manager's Manual FSCK_EXFAT(8)
NAME
fsck_exfat -- Verify and repair ExFAT file systems.
SYNOPSIS
fsck_exfat -q device ...
fsck_exfat [-f] [-p] [-y | -n] [-g | -x] [-d] device ...
DESCRIPTION
The fsck_exfat utility verifies and repairs ExFAT file systems.
The first form of fsck_exfat quickly checks the specified file systems to determine whether they were cleanly unmounted.
The second form of fsck_exfat checks the specified file systems and tries to repair all detected problems, requesting confirmation before
making any changes. The default behavior is to always ask for confirmation of each change. Use the -n or -y options to override this
default behavior.
The device parameter(s) should be a path to a "raw" disk device (a character special device), such as /dev/rdisk1s1. If you specify a "non-
raw" path (a block special device) such as /dev/disk1s1, or just the disk name such as disk1s1, they will automatically be converted to the
corresponding raw disk device (/dev/rdisk1s1).
The options are as follows:
-q Causes fsck_exfat to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the
exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message
is printed to standard output describing whether the volume was clean or dirty.
-f This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for
consistency.
-p Preen the specified file systems. This option is ignored by fsck_exfat and is present only for compatibility with programs
that check other file system types for consistency.
-y Causes fsck_exfat to assume yes as the answer to all questions. It will attempt to repair all problems that are found.
-n Causes fsck_exfat to assume no as the answer to all questions. The device will be opened read-only, and no repairs will be
made.
-g Causes fsck_exfat to produce its output in GUI-compatible form. Each message is printed as a tuple containing the kind of mes-
sage, the message string, and number of parameters to the message string. Any parameters to the message string are printed on
subsequent lines. The message string uses NSLog-like substitutions. This output format is used by applications such as Disk
Utility.
-x Causes fsck_exfat to produce its output in an XML-like form. Each message is printed as a plist(5) containing a message type,
verbosity, message number, and message string. The message string uses NSLog-like substitutions. For message strings that
contain parameters, an array of dictionaries is output. This output format is used by applications such as Disk Utility. It
may be used by other kinds of applications which wish to parse the output of fsck_exfat.
-d Causes fsck_exfat to produce extra debugging output. This generally contains additional details about problems found. When
writing bug reports for fsck_exfat, it is usually helpful to include the output generated from this option.
SEE ALSO
mount_exfat(8), fsck(8)
HISTORY
The fsck_exfat utility first appeared in Mac OS X 10.6.3.
Darwin January 19, 2010 Darwin