On Thu, Mar 17, 2011 at 4:45 PM, JB <jb.1234abcd@gmail.com> wrote:
> Tom H <tomh0665 <at> gmail.com> writes:
>>
>> Thanks. So Linux starts numbering BSD slices after it's done with its
>> own partitions.
>>
>> I presume that if you create sda10, the slices'll start at sda11...
>
> # fdisk -l /dev/sda
> /dev/sda1 * * * * * * *63 * *81920159 * *40960048+ * 7 *HPFS/NTFS
> /dev/sda2 * * * *81920160 * 111222719 * *14651280 * a5 *FreeBSD
> /dev/sda3 * * * 111222720 * 140525279 * *14651280 * 83 *Linux
> /dev/sda4 * * * 140525280 * 255785039 * *57629880 * *5 *Extended
> /dev/sda5 * * * 140525343 * 146391839 * * 2933248+ *82 *Linux swap / Solaris
> /dev/sda6 * * * 146391903 * 158109839 * * 5858968+ *83 *Linux
> /dev/sda7 * * * 158109903 * 187412399 * *14651248+ *83 *Linux
> /dev/sda8 * * * 187412463 * 216714959 * *14651248+ *83 *Linux
> /dev/sda9 * * * 216715023 * 246017519 * *14651248+ *83 *Linux
> /dev/sda10 * * *246017583 * 255785039 * * 4883728+ *83 *Linux
>
> # # dmesg |grep bsd
> [ * *1.572871] *sda2: <bsd: sda11 sda12 sda13 sda14 sda15 >

Thanks. I was planning to test it out tonight. You've saved me the "trouble."


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

JB <jb.1234abcd <at> gmail.com> writes:

> ...
> What would have happened (as I suggested it previously) if I put that FreeBSD
> /dev/sda10 in /etc/fstab ?

> That new Linux /dev/sda10 partition would be auto mounted at that mount point,
> which would presumably be a source of data for some system or user app ...
> ...
This is not an exact statement ...
I meant that in case of:
- a Linux partition /dev/sda10 the boot auto mount would fail due to a mismatch
between UFS mount and its options and Linux partition
- a stand-alone FreeBSD (UFS fs) partition /dev/sda10 the boot auto mount might
be successful with all bad implications

JB



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

I do the same with you .Where I can not mount still

fdisk -l

Device Boot Start End Blocks Id System
/dev/sda1 * 16065 92255936 46119936 7 HPFS/NTFS
/dev/sda2 92256255 459442934 183593340 f W95 Ext'd (LBA)
/dev/sda3 459442935 625126382 82841724 a5 FreeBSD
/dev/sda5 92256256 143456255 25600000 7 HPFS/NTFS
/dev/sda6 143458304 307298303 81920000 7 HPFS/NTFS
/dev/sda7 307300352 309348351 1024000 83 Linux
/dev/sda8 309350400 446566399 68608000 83 Linux
/dev/sda9 446568448 459442175 6436864 82 Linux swap / Solaris


[root@yanxinyou ~]# dmesg | grep bsd
[ 1.708559] sda3: <bsd: sda10 sda11 sda12 sda13 sda14 >

[root@yanxinyou ~]# fdisk /dev/sda

Command (m for help): b
Reading disklabel of /dev/sda3 at sector 459442936.

BSD disklabel command (m for help): p

8 partitions:
# start end size fstype [fsize bsize cpg]
a: 459442935 461540086 2097152 4.2BSD 0 0 0
b: 461540087 469928694 8388608 swap
c: 459442935 625126382 165683448 unused 0 0
d: 469928695 484041462 14112768 4.2BSD 0 0 0
e: 484041463 486138614 2097152 4.2BSD 0 0 0
f: 486138615 625126382 138987768 4.2BSD 0 0 0

BSD disklabel command (m for help): q


[root@yanxinyou ~]# mount -t ufs -o ro,ufstype=ufs2 /dev/sda11 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda11,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so



I think I just enter q . doesn't do any thing before fdisk /dev/sda
So it don't change



2011/3/18 Tom H <tomh0665@gmail.com>:
> On Thu, Mar 17, 2011 at 1:55 PM, JB <jb.1234abcd@gmail.com> wrote:
>> Tom H <tomh0665 <at> gmail.com> writes:
>
>
>>> You then have to pass the options below when mounting (for slice a)
>>> mount -t ufs -o ro,ufstype=ufs2 /dev/sda5 /path/to/mount/point
>>
>> Thanks Tom.
>
> You're welcome.
>
>
>> Here is how it worked for me.
>>
>> # fdisk -l /dev/sda
>> /dev/sda1 * * * * * * *63 * *81920159 * *40960048+ * 7 *HPFS/NTFS
>> /dev/sda2 * * * *81920160 * 111222719 * *14651280 * a5 *FreeBSD
>> /dev/sda3 * * * 111222720 * 140525279 * *14651280 * 83 *Linux
>> /dev/sda4 * * * 140525280 * 246017519 * *52746120 * *5 *Extended
>> /dev/sda5 * * * 140525343 * 146391839 * * 2933248+ *82 *Linux swap / Solaris
>> /dev/sda6 * * * 146391903 * 158109839 * * 5858968+ *83 *Linux
>> /dev/sda7 * * * 158109903 * 187412399 * *14651248+ *83 *Linux
>> /dev/sda8 * * * 187412463 * 216714959 * *14651248+ *83 *Linux
>> /dev/sda9 * * * 216715023 * 246017519 * *14651248+ *83 *Linux
>>
>> # fdisk /dev/sda
>> Command (m for help): b
>> BSD disklabel command (m for help): p
>> *a: 81920160 *82942111 * 1021952 * * 4.2BSD * * * *0 * * 0 * * 0
>> *b: 82942112 *90837066 * 7894955 * * * swap
>> *c: 81920160 *111222719 *29302560 * * unused * * * *0 * * 0
>> *d: 90837067 *92842058 * 2004992 * * 4.2BSD * * * *0 * * 0 * * 0
>> *e: 92842059 *93849674 * 1007616 * * 4.2BSD * * * *0 * * 0 * * 0
>> *f: 93849675 *111222719 *17373045 * * 4.2BSD * * * *0 * * 0 * * 0
>>
>> # mount -t ufs -o ro,ufstype=ufs2 /dev/sda10 /media
>>
>> # mount
>>...
>> /dev/sda10 on /media type ufs (ro,ufstype=ufs2)
>>
>> # ls -al /media
>>...
>> drwxr-xr-x * 2 root root 1024 Mar *2 23:04 bin
>> drwxr-xr-x * 8 root root 1024 Mar *2 22:57 boot
>> ...
>
> Thanks. So Linux starts numbering BSD slices after it's done with its
> own partitions.
>
> I presume that if you create sda10, the slices'll start at sda11...
>
>
>> But, the stuff I documented in a later thread under "Re: FreeBSD Drive Support
>> ??" should not be allowed.
>
> I assume that you're referring to:
>
> <begin>
> # mount -vf -t auto /dev/sda2 /media/
> /dev/sda2 on /media type auto (rw)
>
> # df
> Filesystem * * * * * 1K-blocks * * *Used Available Use% Mounted on
> ...
> /dev/sda2 * * * * * * 14420896 * 7413796 * 5541976 *58% /media
>
> # mount
> ...
> /dev/sda2 on /media type auto (rw)
>
> # 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
> </end>
>
> I'd say that your mount and df commands are confused given that the
> only thing in "/media" after the mount is ".hal-mtab". Bug?
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

On Fri, Mar 18, 2011 at 12:51 AM, xinyou yan <yxy.716@gmail.com> wrote:
>
> I do the same with you .Where I can not mount still
>
> fdisk -l
> * Device Boot * * *Start * * * * End * * *Blocks * Id *System
> /dev/sda1 * * * * * 16065 * *92255936 * *46119936 * *7 *HPFS/NTFS
> /dev/sda2 * * * *92256255 * 459442934 * 183593340 * *f *W95 Ext'd (LBA)
> /dev/sda3 * * * 459442935 * 625126382 * *82841724 * a5 *FreeBSD
> /dev/sda5 * * * *92256256 * 143456255 * *25600000 * *7 *HPFS/NTFS
> /dev/sda6 * * * 143458304 * 307298303 * *81920000 * *7 *HPFS/NTFS
> /dev/sda7 * * * 307300352 * 309348351 * * 1024000 * 83 *Linux
> /dev/sda8 * * * 309350400 * 446566399 * *68608000 * 83 *Linux
> /dev/sda9 * * * 446568448 * 459442175 * * 6436864 * 82 *Linux swap / Solaris
>
>
> [root@yanxinyou ~]# dmesg | grep bsd
> [ * *1.708559] *sda3: <bsd: sda10 sda11 sda12 sda13 sda14 >
>
> [root@yanxinyou ~]# fdisk /dev/sda
>
> Command (m for help): b
> Reading disklabel of /dev/sda3 *at sector 459442936.
>
> BSD disklabel command (m for help): p
>
> 8 partitions:
> # * * * start * * * end * * *size * * fstype * [fsize bsize * cpg]
> *a: 459442935 *461540086 * 2097152 * * 4.2BSD * * * *0 * * 0 * * 0
> *b: 461540087 *469928694 * 8388608 * * * swap
> *c: 459442935 *625126382 *165683448 * * unused * * * *0 * * 0
> *d: 469928695 *484041462 *14112768 * * 4.2BSD * * * *0 * * 0 * * 0
> *e: 484041463 *486138614 * 2097152 * * 4.2BSD * * * *0 * * 0 * * 0
> *f: 486138615 *625126382 *138987768 * * 4.2BSD * * * *0 * * 0 * * 0
>
> BSD disklabel command (m for help): q
>
> [root@yanxinyou ~]# mount -t ufs -o ro,ufstype=ufs2 /dev/sda11 */mnt
> mount: wrong fs type, bad option, bad superblock on /dev/sda11,

sda11 is a swap partition.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

JB <jb.1234abcd <at> gmail.com> writes:

> ...
> While having that /dev/sda10 (FreeBSD slice) mounted as above, I used cfdisk
> and added /dev/sda10 Linux partition (right after /dev/sda9 of course).
>
> To my surprise, I discovered that after that df and mount do not show that
> FreeBSD /dev/sda10 mounted partition ! Magically disappeared

Sorry, not exactly.
The cfdisk action did not cause it of course; it ends with a write command (it
is suggested to reboot to make the changes permanent).
But until that time it creates a presumably semi-permanent state of /dev/sda10
being in cfdisk and fdisk displays, and at the same time df and mount showing
/dev/sda10 mounted as UFS partition on /media mount point.
A subsequent reboot cleared that temporary manual /media mount.

> ...
> What would have happened (as I suggested it previously) if I put that FreeBSD
> /dev/sda10 in /etc/fstab ?
> That new Linux /dev/sda10 partition would be auto mounted at that mount point,
> which would presumably be a source of data for some system or user app ...

That test was done by me.
# cat /etc/fstab
...
/dev/sda10 /media ufs ro,ufstype=ufs2 0 0
...

In this case /dev/sda10 was already a Linux parition per above and the mount
failed as shown in boot log:
# dmesg
...
[ 18.597349] EXT4-fs (sda7): re-mounted. Opts: (null)
[ 18.835869] ufs_read_super: bad magic number
[ 20.743108] Adding 2933244k swap on /dev/sda5. Priority:-1 extents:1
across:2933244k
...

But other bad outcomes are possible (see next post).

> ...

JB


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

JB <jb.1234abcd <at> gmail.com> writes:

> ...

It is apparent that Linux, besides some minor bugs detected here, handles
*BSD file systems in an awkward way.
I say *BSD, as I assume that the FreeBSD test results probably appply to
OpenBSD and NetBSD as well due to similarity in their partition/slices
structure of their installations.

The issue is clear:
Linux kernel assigning device names to *BSD slices following those already
taken by Linux may cause serious problems when disk space is shared by both
OSs, e.g.
# fdisk -l /dev/sda
...
/dev/sda1 63 81920159 40960048+ 7 HPFS/NTFS
/dev/sda2 * 81920160 111222719 14651280 a5 FreeBSD
...
/dev/sda9 216715023 246017519 14651248+ 83 Linux

# dmesg | grep bsd
[ 1.550749] sda2: <bsd: sda10 sda11 sda12 sda13 sda14 >

Handling fellow UNIX OSs well in Linux's space should be a priority.

What are your ideas about solving this issue ?
They could be passed to some senior devs and many younger hot shots who could
attack this problem soon.

JB



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

On 03/18/2011 10:12 AM, JB wrote:
> JB <jb.1234abcd <at> gmail.com> writes:
>
>> ...
>
> It is apparent that Linux, besides some minor bugs detected here, handles
> *BSD file systems in an awkward way.
> I say *BSD, as I assume that the FreeBSD test results probably appply to
> OpenBSD and NetBSD as well due to similarity in their partition/slices
> structure of their installations.
>
> The issue is clear:
> Linux kernel assigning device names to *BSD slices following those already
> taken by Linux may cause serious problems when disk space is shared by both

What kind of problems would it cause?

> OSs, e.g.
> # fdisk -l /dev/sda
> ...
> /dev/sda1 63 81920159 40960048+ 7 HPFS/NTFS
> /dev/sda2 * 81920160 111222719 14651280 a5 FreeBSD
> ...
> /dev/sda9 216715023 246017519 14651248+ 83 Linux
>
> # dmesg | grep bsd
> [ 1.550749] sda2: <bsd: sda10 sda11 sda12 sda13 sda14 >
>
> Handling fellow UNIX OSs well in Linux's space should be a priority.
>
> What are your ideas about solving this issue ?
> They could be passed to some senior devs and many younger hot shots who could
> attack this problem soon.
>
> JB
>
It looks like the FreeBSD partition is being treated like an
extended partition, and the slices as logical partitions.

One thing to keep in mind is that the use of UUID or at least
partition labels are the preferred way to make sure the same
partition is mounted in the same place. It is too easy to change
drive letter designations by changing the boot drive in the BIOS, or
swapping cables to the drives. For that matter, by BIOS lets me set
the device order by drive, regardless of what SATA port the drive is
plugged into. When you get into USB connected storage, it gets even
more confusing when trying to use drive letter/partition to set the
mount point.

Mikkel
--

Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

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

Mikkel <mikkel <at> infinity-ltd.com> writes:

> ...
> What kind of problems would it cause?
>
> > OSs, e.g.
> > # fdisk -l /dev/sda
> > ...
> > /dev/sda1 63 81920159 40960048+ 7 HPFS/NTFS
> > /dev/sda2 * 81920160 111222719 14651280 a5 FreeBSD
> > ...
> > /dev/sda9 216715023 246017519 14651248+ 83 Linux
> >
> > # dmesg | grep bsd
> > [ 1.550749] sda2: <bsd: sda10 sda11 sda12 sda13 sda14 >
> > ...

I would refer you to this thread once more where I described and tested them.

But I will do it one more time:

1. Linux has two widely used partition table display/manipulation entries:
fdisk
cfdisk
and there are more of them.
If none of them show all partitions (inclusive *BSD slices) as in
an example above, then these entries are fooling users and sysadmins.
This is lunacy and can be costly. Believe it or not but users rely on
truthfullness and clarity (nothing shall be hidden) when it comes to
the one and only one source of a particular info, based on which they make
decisions.
What if they decide they need an additional partition and look at fdisk
for the next available (they do not see hidden *BSD slices) ?
Is that not dangerous ?
2. I have shown that *BSD slice /dev/<name> can be temporarily mounted (and
serve as a source of data) and at the same time the same /dev/<name> can
be used to create a new Linux partition.
Is that not dangerous ?
3. I have shown that *BSD slice /dev/<name> can be permanently mounted thru
/etc/fstab (and serve as a source of data) and at the same time the same
/dev/<name> can be used to create a new Linux partition.
After that, due to mismatch of superblock/bad magic number that *BSD mount
will be refused.
Is that not dangerous ?
If that /dev/<name> were used to create a new stand-alone UFS partition
(or anything for that matter that would match UFS superblock/bad magic
number), perhaps the fstab-base auto mount would be successful, serving who
knows what data.
Is that not dangerous ?

JB


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

xinyou yan 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?

Since I don't know where this came from I am guessing here, but it looks as if
that sda2 partition is being treated as a physical disk, perhaps as the one and
only physical drive in a VM. You haven't told us how this partition came about,
but I have seen similar running my BSD VMs.

Therefore: you might try to see if it is the basis of a VM, perhaps with
something like this.

qemu-kvm -m 512 -hda /dev/sda2

That (from command line, obviously) may be enough to get it started if it is in
fact a BSD VM pseudo drive.



--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

On Thu, 04 Aug 2011 03:54:56 -0500, Kevin Williams wrote:

(please, keep the messages in the same thread and avoid using html)

> I'm at the localhost login and out keeps saying my login is incorrect.
> Thanks for the quick reply

Login as root and if you can't try to reset root's password.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.08.04.13.23.02@gmail.com">http://lists.debian.org/pan.2011.08.04.13.23.02@gmail.com