[Bug 330500] Re: Totem crashed at end of video in fullscreen mode

[Jos van Hees]

** Visibility changed to: Public

-- 
Totem crashed at end of video in fullscreen mode
https://bugs.launchpad.net/bugs/330500
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 200747] Re: EXT3-fs error corruption

[Jos van Hees]

I haven't had  this problem ever since.

I therefore do not know the solution. You might want to reconnect your
harddrives, as I did that too while testing for the problem.

Good luck!

Jos

-- 
EXT3-fs error corruption
https://bugs.launchpad.net/bugs/200747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

[Bug 200747] Re: EXT3-fs error corruption

[Jos van Hees]

It happened to me twice - with one day in between. After the second
time, I switched the drives again, found out that the drive was working
and gave it another try.

Ther server now has over three weeks of uptime without getting that
error again. The kernel version is still the same ( 2.6.18-6-686). I
never had it with the other drive, now mounted as secondary, running
debian sid.

Let's hope for me that the problem stays away.

-- 
EXT3-fs error corruption
https://bugs.launchpad.net/bugs/200747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 200747] Re: EXT3-fs error corruption

[Jos van Hees]

That doesn't sound too good.

I've got no idea what's wrong with it, it's working fine here now for over
two days :x.

Have you tried to just reconnect all the cables and/or check if they're nog
broken?

Though that sounds unlikely to me since you're using sata disks.
Also try a e2fsck -f 

This will force a check on your disk. Do the error's stop after one or two
times?
Jos

On Fri, Mar 14, 2008 at 6:55 PM, Fred <[EMAIL PROTECTED]>
wrote:

> Now, I was listening to music in Rhythm box.
> The music was even on sda5, not sdb1.
>
> I was a little bit afk, then came back, and saw applications dim as I
> sat down.
>
> System was going haywire again.
>
> [numbers] EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected
> aborted journal
> [numbers] Remounting filesystem read-only
> [numbers] EXT3-fs error (device sdb1) in ext3_reserve_inode_write: Journal
> has aborted
>
> Then I boot the 7.10 LiveCD.
> [EMAIL PROTECTED]:/var/log$ cat debug | grep -i "ext3"
> Mar 14 17:44:26 ubuntu kernel: [  207.614203] ext3_orphan_cleanup:
> deleting unreferenced inode 1485348
> Mar 14 17:44:26 ubuntu kernel: [  207.614227] ext3_orphan_cleanup:
> deleting unreferenced inode 1485353
> [EMAIL PROTECTED]:/var/log$
>
> [EMAIL PROTECTED]:/var/log$ cat kern.log | grep -i "ext3"
> Mar 14 17:44:26 ubuntu kernel: [   46.415302] EXT3-fs: INFO: recovery
> required on readonly filesystem.
> Mar 14 17:44:26 ubuntu kernel: [   46.415305] EXT3-fs: write access will
> be enabled during recovery.
> Mar 14 17:44:26 ubuntu kernel: [  207.614198] EXT3-fs: sdb1: orphan
> cleanup on readonly fs
> Mar 14 17:44:26 ubuntu kernel: [  207.614203] ext3_orphan_cleanup:
> deleting unreferenced inode 1485348
> Mar 14 17:44:26 ubuntu kernel: [  207.614227] ext3_orphan_cleanup:
> deleting unreferenced inode 1485353
> Mar 14 17:44:26 ubuntu kernel: [  207.614251] EXT3-fs error (device sdb1):
> ext3_free_branches: Read failure, inode=1485353, block=302
> Mar 14 17:44:26 ubuntu kernel: [  207.617633] EXT3-fs error (device sdb1):
> ext3_get_inode_loc: unable to read inode block - inode=1485246,
> block=2981893
> Mar 14 17:44:26 ubuntu kernel: [  207.621596] EXT3-fs warning (device
> sdb1): ext3_orphan_get: bad orphan inode 1485246!  e2fsck was run?
> Mar 14 17:44:26 ubuntu kernel: [  207.621600] ext3_test_bit(bit=125,
> block=2981889) = -1
> Mar 14 17:44:26 ubuntu kernel: [  207.621607] EXT3-fs: sdb1: 2 orphan
> inodes deleted
> Mar 14 17:44:26 ubuntu kernel: [  207.621608] EXT3-fs: recovery complete.
> Mar 14 17:44:26 ubuntu kernel: [  207.621811] EXT3-fs: mounted filesystem
> with ordered data mode.
> Mar 14 17:44:26 ubuntu kernel: [  207.622146] EXT3-fs error (device sdb1):
> ext3_find_entry: reading directory #2 offset 0
>
> [EMAIL PROTECTED]:/var/log$ cat messages | grep -i "ext3"
> Mar 14 17:44:26 ubuntu kernel: [   46.415302] EXT3-fs: INFO: recovery
> required on readonly filesystem.
> Mar 14 17:44:26 ubuntu kernel: [   46.415305] EXT3-fs: write access will
> be enabled during recovery.
> Mar 14 17:44:26 ubuntu kernel: [  207.614198] EXT3-fs: sdb1: orphan
> cleanup on readonly fs
> Mar 14 17:44:26 ubuntu kernel: [  207.621596] EXT3-fs warning (device
> sdb1): ext3_orphan_get: bad orphan inode 1485246!  e2fsck was run?
> Mar 14 17:44:26 ubuntu kernel: [  207.621600] ext3_test_bit(bit=125,
> block=2981889) = -1
> Mar 14 17:44:26 ubuntu kernel: [  207.621607] EXT3-fs: sdb1: 2 orphan
> inodes deleted
> Mar 14 17:44:26 ubuntu kernel: [  207.621608] EXT3-fs: recovery complete.
> Mar 14 17:44:26 ubuntu kernel: [  207.621811] EXT3-fs: mounted filesystem
> with ordered data mode.
>
> [EMAIL PROTECTED]:/var/log$ cat syslog | grep -i "ext3"
> Mar 14 17:44:26 ubuntu kernel: [   46.415302] EXT3-fs: INFO: recovery
> required on readonly filesystem.
> Mar 14 17:44:26 ubuntu kernel: [   46.415305] EXT3-fs: write access will
> be enabled during recovery.
> Mar 14 17:44:26 ubuntu kernel: [  207.614198] EXT3-fs: sdb1: orphan
> cleanup on readonly fs
> Mar 14 17:44:26 ubuntu kernel: [  207.614203] ext3_orphan_cleanup:
> deleting unreferenced inode 1485348
> Mar 14 17:44:26 ubuntu kernel: [  207.614227] ext3_orphan_cleanup:
> deleting unreferenced inode 1485353
> Mar 14 17:44:26 ubuntu kernel: [  207.614251] EXT3-fs error (device sdb1):
> ext3_free_branches: Read failure, inode=1485353, block=302
> Mar 14 17:44:26 ubuntu kernel: [  207.617633] EXT3-fs error (device sdb1):
> ext3_get_inode_loc: unable to read inode block - inode=1485246,
> block=2981893
> Mar 14 17:44:26 ubuntu kernel: [  207.621596] EXT3-fs warning (device
> sdb1): ext3_orphan_get: bad orphan inode 1485246!  e2fsck was run?
> Mar 14 17:44:26 ubuntu kernel: [  207.621600] ext3_test_bit(bit=125,
> block=2981889) = -1
> Mar 14 17:44:26 ubuntu kernel: [  207.621607] EXT3-fs: sdb1: 2 orphan
> inodes deleted
> Mar 14 17:44:26 ubuntu kernel: [  207.621608] EXT3-fs: recovery complete.
> Mar 14 17:44:26 ubuntu kernel: [  207.621811] EXT3-fs: mounted filesystem
> with ordered data mode.
> Mar 14 17:44:26 u

[Bug 200747] Re: EXT3-fs error corruption

[Jos van Hees]

I've got the exact same thing on a freshly installed debian server
(stable).


** Also affects: debian
   Importance: Undecided
   Status: New

-- 
EXT3-fs error corruption
https://bugs.launchpad.net/bugs/200747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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