Re: FreeBSD Drive Support??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/17/2011 08:52 AM, JB wrote:
> James McKenzie<jjmckenzie51<at>  gmail.com>  writes:
>
>> On Thu, Mar 17, 2011 at 1:41 AM, xinyou yan<yxy.716<at>  gmail.com>  wrote:
>>> I have a freebsd system.
>>> In my computer   /dev/sda10 is a freebsd slice.
>>>
>>> I use mount -t ufs /dev/sda10 /tmp
>>> It fail.
>>>
>>> mount: wrong fs type, bad option, bad superblock on /dev/sda10,
>>>        missing codepage or helper program, or other error
>>>        In some cases useful info is found in syslog - try
>>>        dmesg | tail  or so
>>>
>>> How can i mount it?
>> Are you trying to mount this in Fedora?
>>
>> You can try the suggestions JB gave, but FreeBSD might not be using
>> the Unix File System.
>>
>> James McKenzie
> What is actually happening here ?
>
> I have FreeBSD on /dev/sda2.
>
> I do these entries from Fedora 14.
>
> # cfdisk
>                                Disk Drive: /dev/sda
> ...
>      Name        Flags	   Part Type  FS Type          [Label]        Size (MB)
>   ------------------------------------------------------------------------------
>      sda1                    Primary   ntfs                             41943.13
>      sda2        Boot        Primary   ufs                              15002.92
>      sda3                    Primary   ext4                             15002.92
>      sda5                    Logical   swap				3003.68
>      sda6                    Logical   ext3             [backup]		5999.62
>      sda7                    Logical   ext4             [Fedora]        15002.92
>
> # cat /proc/filesystems |grep -i ufs
> 	ufs
>
> # lsmod |grep -i ufs
> ufs                    56786  0
>
> # mount -t auto /dev/sda2 /media/
> mount: wrong fs type, bad option, bad superblock on /dev/sda2,
>         missing codepage or helper program, or other error
>         In some cases useful info is found in syslog - try
>         dmesg | tail  or so
>
> # dmesg |tail
> ...
> [170746.287197] ufs_read_super: bad magic number
> [170949.612767] ufs_read_super: bad magic number
> [170974.503724] ufs_read_super: bad magic number
> [171012.600483] ufs was compiled with read-only support, can't be mounted as
> read-write
> [171043.129655] ufs was compiled with read-only support, can't be mounted as
> read-write
> [171872.818069] ufs was compiled with read-only support, can't be mounted as
> read-write
>
> # man mount
> ...
>        -t, --types vfstype
>                The argument following the -t is used to indicate the filesystem
>                type.   The  filesystem  types  which  are  currently  supported
>                include: ...
>                ..., ufs, ...
> ...
> Mount options for ufs
>         ufstype=value
>                UFS  is a filesystem widely used in different operating systems.
>                The problem are differences among implementations.  Features  of
>                some  implementations are undocumented, so its hard to recognize
>                the type of ufs automatically.  That's why the user must specify
>                the type of ufs by mount option.  Possible values are:
>
>                old    Old  format  of  ufs,  this  is  the  default, read only.
>                       (Don't forget to give the -r option.)
>
>                44bsd  For   filesystems   created   by   a   BSD-like    system
>                       (NetBSD,FreeBSD,OpenBSD).
> ...
>
> # mount -t ufs -o ro,ufstype=44bsd /dev/sda2 /media/
> mount: wrong fs type, bad option, bad superblock on /dev/sda2,
>         missing codepage or helper program, or other error
>         In some cases useful info is found in syslog - try
>         dmesg | tail  or so
>
> # mount -v -t auto /dev/sda2 /media/
> mount: you didn't specify a filesystem type for /dev/sda2
>         I will try type ufs
> mount: wrong fs type, bad option, bad superblock on /dev/sda2,
>         missing codepage or helper program, or other error
>         In some cases useful info is found in syslog - try
>         dmesg | tail  or so
>
> # mount -vf -t auto /dev/sda2 /media/
> /dev/sda2 on /media type auto (rw)
>
> # df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/sda7             14420896   7413796   5541976  58% /
> tmpfs                  1025992       448   1025544   1% /dev/shm
> /dev/sda2             14420896   7413796   5541976  58% /media<========
>
> [root@localhost jb]# mount
> ...
> /dev/sda2 on /media type auto (rw)<========
>
> # cat /proc/mounts
> ...
>                                                                     <====== ???
>
> # ls -al /media
> total 8
> drwxr-xr-x.  2 root root 4096 Mar 17 15:54 .
> dr-xr-xr-x. 23 root root 4096 Mar 14 14:01 ..
> -rw-r--r--   1 root root    0 Mar 14 14:01 .hal-mtab
>
> JB
>
>
Hi all,
As I replied to the original OP, the UFS port in linux
might not be able to mount FreeBSD drives/partitions/slices
if the FreeBSD is sufficiently more recent than the original
UFS port to Linux. A lot of things have changed, and hardly
any attention has been given to the UFS port.

The configuration help menu says:

UFS file system support (read only) (UFS_FS)

CONFIG_UFS_FS:

BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
OpenBSD and NeXTstep) use a file system called UFS. Some System V
Unixes can create and mount hard disk partitions and diskettes using
this file system as well. Saying Y here will allow you to read from
these partitions; if you also want to write to them, say Y to the
experimental "UFS file system write support", below. Please read the
file <file:Documentation/filesystems/ufs.txt> for more information.

The recently released UFS2 variant (used in FreeBSD 5.x) is
READ-ONLY supported.

Note that this option is generally not needed for floppies, since a
good portable way to transport files and directories between unixes
(and even other operating systems) is given by the tar program ("man
tar" or preferably "info tar").

When accessing NeXTstep files, you may need to convert them from the
NeXT character set to the Latin1 character set; use the program
recode ("info recode") for this purpose.

To compile the UFS file system support as a module, choose M here: the
module will be called ufs.

If you haven't heard about all of this before, it's safe to say N.

Symbol: UFS_FS [=m]
Type : tristate
Prompt: UFS file system support (read only)
Defined at fs/ufs/Kconfig:1
Depends on: MISC_FILESYSTEMS [=y] && BLOCK [=y] && BKL [=y]
Location:
-> File systems
-> Miscellaneous filesystems (MISC_FILESYSTEMS [=y])


-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux