William A. Mahaffey III grabbed a keyboard and wrote:
> On 11/12/12 11:10, Tom Furie wrote:
>> On Sun, Nov 11, 2012 at 11:50:20AM -0600, William A. Mahaffey III wrote:
>>
>>> [root@opty165a:/etc, Sun Nov 11, 11:44 AM] 593 # mount -t ext3
>>> /dev/ad0s1 /mnt
>>> mount: /dev/ad0s1 : No such device
>>> [root@opty165a:/etc, Sun Nov 11, 11:44 AM] 594 # mount -t ext3
>>> /dev/ad6s1 /mnt
>>> mount: /dev/ad6s1 : No such device
>>> [root@opty165a:/etc, Sun Nov 11, 11:44 AM] 595 #
>>>
>>> Both drives were AOK as of Friday when I poweroff'ed the CentOS
>>> rescue disk to replace the root drive, so I *think* they are OK.
>>> They were recognized during the install as ext3 drives. The new root
>>> drive is ad4, a 160 GB SATA drive. What's going on here ? Isn't the
>>> ext3 fs supported under Debian-kfreeBSD ? TIA for any clues& happy
>>> Veteran's Day.
>> Are you able to mount those filesystems as ext2? Any ext3 filesystem
>> should be mountable as ext2.
>
> Hmmmmm .... Really ? I've never heard that, what about journalling ? I
> would like to non-destructively access them, & I wasn't aware of that ....
Yup. Both ext3 & ext4 are built to be backwards compatible. The only
thing you lose by using ext2 is the journal. Well, you lose the ability
to handle the larger file sizes that ext3 & ext4 support, but I'm not
sure what form such an incompatibility.
A decent comparison of the formats can be found here, among other places:
http://www.thegeekstuff.com/2011/05/ext2-ext3-ext4/
> Tried it:
>
> [root@opty165a:/etc, Mon Nov 12, 02:12 PM] 802 # mount -t ext3 /dev/ad6s1 /mnt
> mount: /dev/ad6s1 : No such device
> [root@opty165a:/etc, Mon Nov 12, 02:13 PM] 803 # mount -t ext2 /dev/ad6s1 /mnt
> mount: /dev/ad6s1 : No such device
> [root@opty165a:/etc, Mon Nov 12, 02:13 PM] 804 # df
> Filesystem Type 1K-blocks Used Available Use% Mounted on
> /dev/ad4s3 ufs 146640898 435318 134474310 1% /
> devfs devfs 1 1 0 100% /dev
> linprocfs
> linprocfs 4 4 0 100% /proc
> /sys sysfs 4 4 0 100% /sys
> fdescfs fdescfs 1 1 0 100% /dev/fd
> tmpfs tmpfs 5536380 4 5536376 1% /lib/init/rw
> /dev/ad4s1 ext2fs 914501 6515 859193 1% /boot
> [root@opty165a:/etc, Mon Nov 12, 02:13 PM] 805 #
>
>
> I go back to my original question: Is ext3fs supported under
> debian-kfreeBSD ? Ext3fs is only supported '-ro', i.e. read-only by the
> various *BSD's, AFAIK, *not* '-rw', i.e. *not* read-write, not
> full-native fs support, does that restriction carry over to
> debian-kfreeBSD ?
Don't know what to tell you here. That error message typically means
that the mount command doesn't see the presence of the device you're
trying to mount (in this case, /dev/ad6s1). It doesn't look like it's
complaining about a non-supported file system type; it's complaining
that it doesn't see the device. You may see the device via other
methods that you're using to see the presence of it, but *mount* doesn't
see it for whatever reason. I'm assuming that when you do a "ls -l" on
/dev, you actually see a device called /dev/ad6s1....
Question: What does your /etc/mtab file show for the /dev/ad4s3 mount?
In a Linux system, typically a IDE drive (PATA) would be referred to by
the system as /dev/hdx and a SATA or SCSI drive would be /dev/sdx. I
did some searching to find out about /dev/adx, and it's a BSD thing.
While doing that search I found that FreeBSD itself is supposed to have
some support for non-native (ufs, ffs) file systems such as ext; you'd
think that a Debian build would include that....
One other question here, and sorry if you've already answered this, but
is there some specific reason why you want to run Debian with a FreeBSD
kernel instead of the standard Linux one? (Just a point of curiosity.)
--Dave
Attachment:
signature.asc
Description: OpenPGP digital signature