[Bug 118256] Re: ext3 data corruption with kernel 2.6.20-16-generic

2007-09-21 Thread Launchpad Janitor
*** This bug is a duplicate of bug 53102 ***
https://bugs.launchpad.net/bugs/53102

[Expired for linux-source-2.6.20 (Ubuntu) because there has been no
activity for 60 days.]

-- 
ext3 data corruption with kernel  2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 118256] Re: ext3 data corruption with kernel 2.6.20-16-generic

2007-06-25 Thread Tero Karvinen
*** This bug is a duplicate of bug 53102 ***
https://bugs.launchpad.net/bugs/53102

** This bug has been marked a duplicate of bug 53102
   Ext3 filesystem corruption - data loss

-- 
ext3 data corruption with kernel  2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 118256] Re: ext3 data corruption with kernel 2.6.20-16-generic

2007-06-17 Thread Tero Karvinen
** Tags added: corruption ext3

-- 
ext3 data corruption with kernel  2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 118256] Re: ext3 data corruption with kernel 2.6.20-16-generic

2007-06-01 Thread yamal
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.20

-- 
ext3 data corruption with kernel  2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 118256] Re: ext3 data corruption with kernel 2.6.20-16-generic

2007-06-01 Thread Jérôme Guelfucci
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already 
done so (please pay attention to lspci's additional options), as required by 
the Ubuntu Kernel Team:
1. Please include the output of the command uname -a in your next response. 
It should be one, long line of text which includes the exact kernel version 
you're running, as well as the CPU architecture.
2. Please run the command dmesg  dmesg.log and attach the resulting file 
dmesg.log to this bug report.
3. Please run the command lspci -vvnn  lspci-vvnn.log and attach the 
resulting file lspci-vvnn.log to this bug report.

For your reference, the full description of procedures for kernel-
related bug reports is available at [WWW]
http://wiki.ubuntu.com/KernelTeamBugPolicies

** Changed in: linux-source-2.6.20 (Ubuntu)
   Importance: Undecided = Medium
   Status: Unconfirmed = Needs Info

-- 
ext3 data corruption with kernel  2.6.20-16-generic
https://bugs.launchpad.net/bugs/118256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 118256] Re: ext3 data corruption with kernel 2.6.20-16-generic

2007-06-01 Thread frodri
Hi,

Thanks for your reply.  The system is currently running a livecd boot,
since I am trying to rescue as much data as possible.  However, I think
that most information is readily available.  For instance, the dmesg
output is already shown in the logs I submited, and I have copied it to
this bug report (cat /var/log/dmesg  dmesg).  As for uname -a, this
should be:

 Linux ubuntu 2.6.20-16-generic #2 SMP Wed May 23 00:30:47 UTC 2007
x86_64 GNU/Linux

And lastly, for the lspci, I have attached the output.

Hope this is enough, but if anything else is needed please let me know.


Best regards,

Fernando Rodriguez



(as shown in the logs as well).

Jérôme Guelfucci wrote:
 Thanks for taking the time to report this bug. Unfortunately we can't
 fix it, because your description doesn't yet have enough information.

 Please include the following additional information, if you have not already 
 done so (please pay attention to lspci's additional options), as required by 
 the Ubuntu Kernel Team:
 1. Please include the output of the command uname -a in your next response. 
 It should be one, long line of text which includes the exact kernel version 
 you're running, as well as the CPU architecture.
 2. Please run the command dmesg  dmesg.log and attach the resulting file 
 dmesg.log to this bug report.
 3. Please run the command lspci -vvnn  lspci-vvnn.log and attach the 
 resulting file lspci-vvnn.log to this bug report.

 For your reference, the full description of procedures for kernel-
 related bug reports is available at [WWW]
 http://wiki.ubuntu.com/KernelTeamBugPolicies

 ** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Needs Info

   


[0.00] Linux version 2.6.20-16-generic ([EMAIL PROTECTED]) (gcc version 
4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Wed May 23 00:30:47 UTC 2007 (Ubuntu 
2.6.20-16.28-generic)
[0.00] Command line: root=UUID=e0637d37-2f17-477b-ac67-735af4c1634a ro 
quiet splash
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009fc00 (usable)
[0.00]  BIOS-e820: 0009fc00 - 000a (reserved)
[0.00]  BIOS-e820: 000e - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 7fff (usable)
[0.00]  BIOS-e820: 7fff - 7000 (ACPI data)
[0.00]  BIOS-e820: 7000 - 8000 (ACPI NVS)
[0.00]  BIOS-e820: ff78 - 0001 (reserved)
[0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used
[0.00] Entering add_active_range(0, 256, 524272) 1 entries of 3200 used
[0.00] end_pfn_map = 1048576
[0.00] DMI 2.3 present.
[0.00] ACPI: RSDP (v002 ACPIAM) @ 
0x000f6e00
[0.00] ACPI: XSDT (v001 A M I  OEMXSDT  0x05000506 MSFT 0x0097) @ 
0x7fff0100
[0.00] ACPI: FADT (v001 A M I  OEMFACP  0x05000506 MSFT 0x0097) @ 
0x7fff0281
[0.00] ACPI: MADT (v001 A M I  OEMAPIC  0x05000506 MSFT 0x0097) @ 
0x7fff0380
[0.00] ACPI: OEMB (v001 A M I  OEMBIOS  0x05000506 MSFT 0x0097) @ 
0x7040
[0.00] ACPI: HPET (v001 A M I  OEMHPET  0x05000506 MSFT 0x0097) @ 
0x7fff4260
[0.00] ACPI: ASF! (v001 AMIASF AMDSTRET 0x0001 INTL 0x02002026) @ 
0x7fff42a0
[0.00] ACPI: DSDT (v001  0 0001 0x0001 INTL 0x02002026) @ 
0x
[0.00] Scanning NUMA topology in Northbridge 24
[0.00] Number of nodes 2
[0.00] Node 0 using interleaving mode 1/0
[0.00] No NUMA configuration found
[0.00] Faking a node at -7fff
[0.00] Entering add_active_range(0, 0, 159) 0 entries of 3200 used
[0.00] Entering add_active_range(0, 256, 524272) 1 entries of 3200 used
[0.00] Bootmem setup node 0 -7fff
[0.00] Zone PFN ranges:
[0.00]   DMA 0 - 4096
[0.00]   DMA324096 -  1048576
[0.00]   Normal1048576 -  1048576
[0.00] early_node_map[2] active PFN ranges
[0.00] 0:0 -  159
[0.00] 0:  256 -   524272
[0.00] On node 0 totalpages: 524175
[0.00]   DMA zone: 56 pages used for memmap
[0.00]   DMA zone: 1087 pages reserved
[0.00]   DMA zone: 2856 pages, LIFO batch:0
[0.00]   DMA32 zone: 7111 pages used for memmap
[0.00]   DMA32 zone: 513065 pages, LIFO batch:31
[0.00]   Normal zone: 0 pages used for memmap
[0.00] ACPI: PM-Timer IO Port: 0x5008
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[0.00] Processor #0 (Bootup-CPU)
[0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[0.00] Processor