Rahul Sundaram wrote:
> Christopher Brown wrote:
>> Fair enough. I'll settle for default on F11 then.
>
> Considering the btrfs roadmap, It might very well be the default. Eric
> Sandeen seems to have missed his only opportunity ;-)

btrfs is making great progress, Rahul, but I'd be willing to place a
small wager on it *not* being the default for F11

-Eric

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

2008/10/10 Peter Robinson <pbrobinson@gmail.com>:
>>>>> (*)Yes, this does indicate that the ext4 developers feel it's time to
>>>>> move on past the "dev" stage; as the patch says "The ext4 filesystem is
>>>>> getting stable enough that it's time to drop the "dev" prefix." - as
>>>>> with any filesystem, though, I still encourage you to back up important
>>>>> data
>>>>
>>>> Does this mean ext4 will be available as generic during
>>>> installs/upgrades, same as ext3? Or does it have to be given as an
>>>> option during install to get it to show up?
>>>
>>> it still takes the ext4 option on boot.
>>
>> Oh come on - that makes it barely differential between
>> iamanext4developer. Put your nuts on the line and offer it up as an
>> additional option on install - I dare you. I thought Fedora was
>> bleeding edge! I miss that heart-racing feeling when I _just dont
>> know_ if my data is coming back up on reboot...
>
> Are you going to put your nuts on the line and provide the support to
> the end users when they don't get their data back on reboot?

Sure, its called #fedora-ext4 with a bot spitting out the word
'backup' on every /join

--
Christopher Brown

http://www.chruz.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Oct 10, 2008 at 12:10 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> Eric Sandeen wrote:
>
>> Changing /etc/fstab to list "ext4" for the root fs may be enough, do it
>> before you install the new kernel.
>
> On further reflection, you will probably just have to do this.
>
> -Eric
>
>> notting suggested a module alias to ext4dev in the ext4.ko module
>> itself, that sounds like a good plan and as long as it gets upstream
>> I'll commit it to Fedora shortly, and I think that should make it all
>> seamless.
>
>
I have an 'ext4' FS on a USB hard drive. When I plug this in, I get a
"Cannot mount volume" popup:

The volume 'Backup1' uses the ext4dev file system which is not
supported by your system, followed by a dbus-type failure error
message about a minute later.

This just me, or what additional changes are needed?

tom
--
Tom London

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Sat, Oct 11, 2008 at 12:19 PM, Tom London <selinux@gmail.com> wrote:
> On Fri, Oct 10, 2008 at 12:10 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>> Eric Sandeen wrote:
>>
>>> Changing /etc/fstab to list "ext4" for the root fs may be enough, do it
>>> before you install the new kernel.
>>
>> On further reflection, you will probably just have to do this.
>>
>> -Eric
>>
>>> notting suggested a module alias to ext4dev in the ext4.ko module
>>> itself, that sounds like a good plan and as long as it gets upstream
>>> I'll commit it to Fedora shortly, and I think that should make it all
>>> seamless.
>>
>>
> I have an 'ext4' FS on a USB hard drive. When I plug this in, I get a
> "Cannot mount volume" popup:
>
> The volume 'Backup1' uses the ext4dev file system which is not
> supported by your system, followed by a dbus-type failure error
> message about a minute later.
>
> This just me, or what additional changes are needed?
>
> tom
> --
Well, the "--fstype" option to gnome-mount works for manual command:
"gnome-mount -d /dev/sdb1 --fstype ext4"

So I'm not road blocked. The "plug and play" auto mounting doesn't work though.

tom
--
Tom London

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Tom London wrote:
> On Fri, Oct 10, 2008 at 12:10 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>> Eric Sandeen wrote:
>>
>>> Changing /etc/fstab to list "ext4" for the root fs may be enough, do it
>>> before you install the new kernel.
>> On further reflection, you will probably just have to do this.
>>
>> -Eric
>>
>>> notting suggested a module alias to ext4dev in the ext4.ko module
>>> itself, that sounds like a good plan and as long as it gets upstream
>>> I'll commit it to Fedora shortly, and I think that should make it all
>>> seamless.
>>
> I have an 'ext4' FS on a USB hard drive. When I plug this in, I get a
> "Cannot mount volume" popup:
>
> The volume 'Backup1' uses the ext4dev file system which is not
> supported by your system, followed by a dbus-type failure error
> message about a minute later.
>
> This just me, or what additional changes are needed?

Do you have the most recent e2fsprogs? And/or what does blkid
/dev/whatever say... if it says ext4dev, try newer e2fsprogs - blkid had
a bug that caused it to say "ext4dev" when "ext4" is what we wanted.

Going forward I think we'll register both ext4 & ext4dev from the ext4
kernel module, at least for a while, so that "mount -t ext4dev" will
work still work in the transition period.

Sorry for all the hassle

-Eric

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Sat, Oct 11, 2008 at 2:45 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> Tom London wrote:
>> On Fri, Oct 10, 2008 at 12:10 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>>> Eric Sandeen wrote:
>>>
>>>> Changing /etc/fstab to list "ext4" for the root fs may be enough, do it
>>>> before you install the new kernel.
>>> On further reflection, you will probably just have to do this.
>>>
>>> -Eric
>>>
>>>> notting suggested a module alias to ext4dev in the ext4.ko module
>>>> itself, that sounds like a good plan and as long as it gets upstream
>>>> I'll commit it to Fedora shortly, and I think that should make it all
>>>> seamless.
>>>
>> I have an 'ext4' FS on a USB hard drive. When I plug this in, I get a
>> "Cannot mount volume" popup:
>>
>> The volume 'Backup1' uses the ext4dev file system which is not
>> supported by your system, followed by a dbus-type failure error
>> message about a minute later.
>>
>> This just me, or what additional changes are needed?
>
> Do you have the most recent e2fsprogs? And/or what does blkid
> /dev/whatever say... if it says ext4dev, try newer e2fsprogs - blkid had
> a bug that caused it to say "ext4dev" when "ext4" is what we wanted.
>
> Going forward I think we'll register both ext4 & ext4dev from the ext4
> kernel module, at least for a while, so that "mount -t ext4dev" will
> work still work in the transition period.
>
> Sorry for all the hassle
>
> -Eric
>
No hassle, this is fun!

Anyway:

[root@tlondon ~]# rpm -q e2fsprogs
e2fsprogs-1.41.2-2.fc10.i386
[root@tlondon ~]# blkid /dev/sdb1
/dev/sdb1: LABEL="Backup1" UUID="7066e635-fe1f-4cf8-94a6-1a3e9229a44c"
TYPE="ext4"
[root@tlondon ~]#

Guessing that something is compiled with 'ext4dev' (not 'ext4'), I did
'strings | grep ext4' in the usual places (/bin, /sbin, /usr/bin,
/usr/sbin/, /usr/libexec, /usr/lib). Here is what I got (omitting
those that appeared to have both 'ext4' and ext4dev'):

/sbin/quotacheck
ext4dev
/sbin/quotaoff
ext4dev
/sbin/quotaon
ext4dev
/usr/bin/quota
ext4dev
/usr/sbin/convertquota
ext4dev
/usr/sbin/edquota
ext4dev
/usr/sbin/repquota
ext4dev
/usr/sbin/rpc.rquotad
ext4dev
/usr/sbin/setquota
ext4dev
/usr/sbin/warnquota
ext4dev

So I'm guessing those (all quota related) need updating. Don't think
this has anything to do with my 'issue', however.

Anyway, I can mount manually for now. Sorry I couldn't quickly figure
out what was doing this.....

tom
--
Tom London

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Tom London wrote:
> On Sat, Oct 11, 2008 at 2:45 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>> Tom London wrote:
>>> On Fri, Oct 10, 2008 at 12:10 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>>>> Eric Sandeen wrote:
>>>>
>>>>> Changing /etc/fstab to list "ext4" for the root fs may be enough, do it
>>>>> before you install the new kernel.
>>>> On further reflection, you will probably just have to do this.
>>>>
>>>> -Eric
>>>>
>>>>> notting suggested a module alias to ext4dev in the ext4.ko module
>>>>> itself, that sounds like a good plan and as long as it gets upstream
>>>>> I'll commit it to Fedora shortly, and I think that should make it all
>>>>> seamless.
>>> I have an 'ext4' FS on a USB hard drive. When I plug this in, I get a
>>> "Cannot mount volume" popup:
>>>
>>> The volume 'Backup1' uses the ext4dev file system which is not
>>> supported by your system, followed by a dbus-type failure error
>>> message about a minute later.
>>>
>>> This just me, or what additional changes are needed?
>> Do you have the most recent e2fsprogs? And/or what does blkid
>> /dev/whatever say... if it says ext4dev, try newer e2fsprogs - blkid had
>> a bug that caused it to say "ext4dev" when "ext4" is what we wanted.
>>
>> Going forward I think we'll register both ext4 & ext4dev from the ext4
>> kernel module, at least for a while, so that "mount -t ext4dev" will
>> work still work in the transition period.
>>
>> Sorry for all the hassle
>>
>> -Eric
>>
> No hassle, this is fun!
>
> Anyway:
>
> [root@tlondon ~]# rpm -q e2fsprogs
> e2fsprogs-1.41.2-2.fc10.i386
> [root@tlondon ~]# blkid /dev/sdb1
> /dev/sdb1: LABEL="Backup1" UUID="7066e635-fe1f-4cf8-94a6-1a3e9229a44c"
> TYPE="ext4"
> [root@tlondon ~]#
>
> Guessing that something is compiled with 'ext4dev' (not 'ext4'), I did
> 'strings | grep ext4' in the usual places (/bin, /sbin, /usr/bin,
> /usr/sbin/, /usr/libexec, /usr/lib). Here is what I got (omitting
> those that appeared to have both 'ext4' and ext4dev'):
>
> /sbin/quotacheck
> ext4dev

crud, you're right:

#define MNTTYPE_EXT4 "ext4dev" /* ext4 filesystem */

we'll need to update that.

Thanks,
-Eric

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Tom London wrote:
>

> Anyway, I can mount manually for now. Sorry I couldn't quickly figure
> out what was doing this.....
>
> tom

Actually, I wasn't thinking; hal uses udev not blkid; udev will also
need updates. Registering both fs types will help, I'll get that done soon.

/me wishes the ext4dev thing had never come into existence right about now.

But we'll get it fixed up.

Thanks,
-Eric

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Sat, Oct 11, 2008 at 6:04 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> Tom London wrote:
>>
>
>> Anyway, I can mount manually for now. Sorry I couldn't quickly figure
>> out what was doing this.....
>>
>> tom
>
> Actually, I wasn't thinking; hal uses udev not blkid; udev will also
> need updates. Registering both fs types will help, I'll get that done soon.
>
> /me wishes the ext4dev thing had never come into existence right about now.
>
> But we'll get it fixed up.
>
> Thanks,
> -Eric
>
OK, this is getting spooky....

After "forcing" gnome-mount (via "gnome-mount -d /dev/sdb1 --fstype
ext4"), and unmounting (via gnome-mount -u), I rebooted and forgot to
power off/unplug the USB drive.

After gdm login, the system had no problem mounting the ext4
filesystem (/media/Backup1 was "just there").

Now, each time I "plug in" the USB drive, it just automagically mounts
the ext4 FS without any complaints or problems.

I can only guess that something was "caching" the filesystem type
(udev?) somewhere....

On the up side, this is now "just working" for me. On the down side,
not sure I can help debug this any longer....

Make sense to you?

tom
--
Tom London

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Tom London wrote:

> OK, this is getting spooky....
>
> After "forcing" gnome-mount (via "gnome-mount -d /dev/sdb1 --fstype
> ext4"), and unmounting (via gnome-mount -u), I rebooted and forgot to
> power off/unplug the USB drive.
>
> After gdm login, the system had no problem mounting the ext4
> filesystem (/media/Backup1 was "just there").
>
> Now, each time I "plug in" the USB drive, it just automagically mounts
> the ext4 FS without any complaints or problems.
>
> I can only guess that something was "caching" the filesystem type
> (udev?) somewhere....
>
> On the up side, this is now "just working" for me. On the down side,
> not sure I can help debug this any longer....
>
> Make sense to you?
>
> tom

I'm honestly not as up to speed on udev as I probably should be, but
I've seen Ted make references before to needing reboots before new
filesystems can be recognized via udev... perhaps it's the same thing.

-Eric

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list