What is the Solaris filesystem called?

Thaidog · 04-07-2005, 12:24 AM

I know zfs is the new flesystem in Solaris 10... but what is the old filesystem called?

jlliagre · 04-07-2005, 01:36 AM

Solaris own's filesystem is UFS (Unix FileSystem).
zfs is not yet in Solaris 10.

vharishankar · 04-07-2005, 01:37 AM

UFS? I googled around and I presume UFS was the older filesystem used by Solaris.

EDIT: jlliagre got ahead of me on this one.

jlliagre · 04-07-2005, 03:12 AM

Both are true.
Part of the confusion comes from some sites describing UFS (actually UFS1) as a an obsolete filesystem preceding BSD's FFS and ignore Sun's implementation.

UFS (UFS3) is the filesystem SunOS successive versions use since the early eighties, based on berkeley (BSD) FFS fast file system.
Sun has improved it with time, with current features like multi-terabytes support, journaling, snapshots, ...

As both FFS and UFS, amongst others, are very similar, Linux is using a single driver for both, and an option is telling which one to target, e.g.:

Code:

 
mount -t ufs -o ufstype=44bsd /dev/hda8 /mnt

With Solaris ufs, the option would be: "ufstype=sunx86"

lyonsd · 06-05-2005, 11:08 PM

Quote:

Originally posted by jlliagre
Both are true.
Part of the confusion comes from some sites describing UFS (actually UFS1) as a an obsolete filesystem preceding BSD's FFS and ignore Sun's implementation.

UFS (UFS3) is the filesystem SunOS successive versions use since the early eighties, based on berkeley (BSD) FFS fast file system.
Sun has improved it with time, with current features like multi-terabytes support, journaling, snapshots, ...

As both FFS and UFS, amongst others, are very similar, Linux is using a single driver for both, and an option is telling which one to target, e.g.:

Code:

mount -t ufs -o ufstype=44bsd /dev/hda8 /mnt

With Solaris ufs, the option would be: "ufstype=sunx86"

Doesn't work for me....

Code:

# mount -t ufs -o ufstype=44bsd /dev/hdb1 /mnt/solaris/
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
# dmesg|tail
ufs was compiled with read-only support, can't be mounted as read-write
# mount -t ufs -o ufstype=44bsd,ro /dev/hdb1 /mnt/solaris/
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
# dmesg|tail
ufs was compiled with read-only support, can't be mounted as read-write
ufs_read_super: bad magic number
# mount -t ufs -o ufstype=sunx86,ro /dev/hdb1 /mnt/solaris/
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
# dmesg|tail
ufs was compiled with read-only support, can't be mounted as read-write
ufs_read_super: bad magic number
ufs_read_super: bad magic number

Since there are slices within a Solaris partition, how does one realize them on the mount command line?

jlliagre · 06-06-2005, 01:30 AM

Slices are handled by linux the same way as extended partitions.
That explains why your hdb1 mount fails. hdb1 doesn't contain a single ufs filesystem.
cat /proc/partitions, or better "dmesg | grep hda" should tell you the right device name to use for you Solaris slices, e.g.:

Code:

hda: max request size: 1024KiB
hda: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4
hda1: <solaris: [s0] hda5 [s1] hda6 [s2] hda7 >

By the way, this is the same with BSD.