Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 167562
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Maurice Volaski <mvolaski@aecom.yu.edu>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 167562 depends on: Show dependency tree
Bug 167562 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-02-19 01:30 0000 
Ext4 is intended for development, not mainstream use. The patches for it are
summarily being included in 1.39-r1 per bug 156697.

These patches causes problems. For one, when I tried to initialize a 2+ TB
filesystem, the 64bit flag was applied, but ext3 in the kernel does not about
this flag and it was not able to use the filesystem. Presumably, there could be
other problems.

Please see messages on the ext3 mailing list posted by the programmer:
https://www.redhat.com/archives/ext3-users/2007-February/msg00014.html
and
https://www.redhat.com/archives/ext3-users/2007-February/msg00017.html

I suggest providing a separate ebuild for a version containing the patches and
masking that version everywhere.

------- Comment #1 From SpanKY 2007-02-27 15:31:34 0000 ------- 
*** Bug 168315 has been marked as a duplicate of this bug. ***

------- Comment #2 From Mikko Tiihonen 2007-03-17 09:35:44 0000 ------- 
With ext4 patches the e2fsprogs does not even pass its own tests, see bug
#159834.

Could we at least have an ext4 USE flag to control applying of the patches?
And if enabled print a warning that the tool is not fully compatible with ext3.

------- Comment #3 From Maurice Volaski 2007-03-17 21:02:30 0000 ------- 
That sounds reasonable to me.

------- Comment #4 From SpanKY 2007-03-24 08:49:36 0000 ------- 
*** Bug 159834 has been marked as a duplicate of this bug. ***

------- Comment #5 From SpanKY 2007-03-24 08:52:15 0000 ------- 
fixed in 1.39-r2

------- Comment #6 From Radoslaw Szkodzinski 2007-04-04 06:40:32 0000 ------- 
It's not fixed.

You didn't provide ext4 flag or ebuild.
I have to mask the newer version just to use ext4 - and this means I won't get
the newest fixes.

------- Comment #7 From SpanKY 2007-04-04 07:17:15 0000 ------- 
nor do i plan to

if you want ext4, use 1.39-r1 until it gets merged into a real version

------- Comment #8 From crypt 2007-04-25 17:42:38 0000 ------- 
 (In reply to comment #7)
> nor do i plan to
> 
> if you want ext4, use 1.39-r1 until it gets merged into a real version
> 

Grreate! And now when you've droped ext4 support and my system at work doesn't
boot I must search in bug list, why. Ofcause, i fix my trouble, but would you
possible to do more correct fixes next time.

------- Comment #9 From SpanKY 2007-05-04 22:04:16 0000 ------- 
maybe some day if you are a developer you can make these sort of calls ...
until then, you're not having to maintain the package, so you can deal with the
reality

------- Comment #10 From Jakub Moc (RETIRED) 2008-03-02 18:43:40 0000 ------- 
*** Bug 212099 has been marked as a duplicate of this bug. ***
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug