View Issue Details

IDProjectCategoryView StatusLast Update
0002494ardourbugspublic2020-04-19 20:13
Reporterameisevinyl Assigned Topaul  
PrioritynormalSeveritycrashReproducibilityrandom
Status closedResolutionno change required 
Product Version2.7 
Summary0002494: ardour destroyed ext3 fs
DescriptionI have been working with ardour on ubuntu 8.10 with the ubuntu 8.04 rt kernel.
I got ardour 2.7 from getdeb,
after importing several wave-files and adding these regions to an audio track
playing them back through jack/freebob
ardour complains that /dev/sda5 (my big linux / partition) is not
writeable anymore (read-only system), session cannot be saved anymore,
system crashes.
jack is still running.
an immediate fsck.ext3 shows a lot of errrors.
this happend nearly everytime i used ardour for longer than 20-30mins.
last consequence was a GRUB ERROR 15 a total system crash
leaving me with an not fixable ext3 partition.

TagsNo tags attached.

Activities

thorgal

2008-12-17 13:26

reporter   ~0005533

boot a rescue disk, USB drive, or any other external bootable system. Fix your partition from the rescue system. Hopefully, you'll recover your data.

ameisevinyl

2009-01-09 11:54

reporter   ~0005576

@thorgal,thanks yes i tried that but it was too late,
i got a big lost&found folder and could atleast copy all my jpg
from my photoalbum to usb-disk.
i am now back on ubuntu LTS hopefully the more stable environment
for audio and ardour

thorgal

2009-01-09 12:52

reporter   ~0005577

Last edited: 2009-01-09 12:53

wow, that's a bit sad to hear. What HD are you using ?
It happened to me as well with Ubuntu (about 1.5 year ago), I fucked up an ext3 partition that made my system unusable (it contained / and /boot). I'll never use Ubuntu again for specific systems like a DAW. I don't know what they do to the debian base stuff they derive Ubuntu from, but debian never ever blew on me like that.

paul

2009-01-15 21:03

administrator   ~0005613

no application can "destroy" a filesystem. i regret that you suffered damage to one or more of your filesystems while running ardour, but the damage was not done by ardour - there is no way for ardour to do this. something was wrong with your kernel, your hardware or both.

system

2020-04-19 20:13

developer   ~0021842

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2008-12-17 13:13 ameisevinyl New Issue
2008-12-17 13:26 thorgal Note Added: 0005533
2009-01-09 11:54 ameisevinyl Note Added: 0005576
2009-01-09 12:52 thorgal Note Added: 0005577
2009-01-09 12:53 thorgal Note Edited: 0005577
2009-01-15 21:03 paul cost => 0.00
2009-01-15 21:03 paul Status new => resolved
2009-01-15 21:03 paul Resolution open => no change required
2009-01-15 21:03 paul Assigned To => paul
2009-01-15 21:03 paul Note Added: 0005613
2010-04-24 10:28 cth103 Category bugs => bugs2
2010-04-24 10:32 cth103 Category bugs2 => bugs
2020-04-19 20:13 system Note Added: 0021842
2020-04-19 20:13 system Status resolved => closed