[pacman-dev] database on separate fs and inodes
Hi Long story short: (before signing new bug i want to be sure) After putting /var/lib/pacman on separate fs (raid1) i just messed things a little and run out of inodes. # fsck.ext2 -pfv /dev/md1 18072 inodes used (100.00%) Most important is what pacman did. So after -Syu packages were updated and no changes in db was made. Most important is that i pacman didn't show any error msg about that. Today i trayed -Syu again i got last time installed packages list added to new one. Pacman showed only packages list and size then just quit w/o any error again. Now I'm trying to repair db and reproduce bug, but i think that quick fix for that is to make small change in pacman that first he will tray to write db entry then packages files to disk. Sorry for my 'bad' English i hope that all catch my drift.
Hi Long story short: (before signing new bug i want to be sure) I suggest you to open a new task for this in FS; if this hasn't been reported yet. After putting /var/lib/pacman on separate fs (raid1) i just messed things a little and run out of inodes.
# fsck.ext2 -pfv /dev/md1 18072 inodes used (100.00%)
Most important is what pacman did. So after -Syu packages were updated and no changes in db was made. Most important is that i pacman didn't show any error msg about that.
Today i trayed -Syu again i got last time installed packages list added to new one. Pacman showed only packages list and size then just quit w/o any error again.
Now I'm trying to repair db and reproduce bug, but i think that quick fix for that is to make small change in pacman that first he will tray to write db entry then packages files to disk.
Sorry for my 'bad' English i hope that all catch my drift.
Yes, this is a critical bug imho. To be short: At this moment pacman cannot rollback transaction (but it is planned: FS#8585) What is even worse (extra bug), it doesn't inform you about unsuccessful db operations (if I didn't misunderstand you); but you could probably do an ugly hack to fix things (or ask somebody to help <- pacman.log is important here) Bye ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/
Dnia Fri, 16 Nov 2007 13:12:13 +0100 Nagy Gabor <ngaba@bibl.u-szeged.hu> napisał(a):
Hi Long story short: (before signing new bug i want to be sure) I suggest you to open a new task for this in FS; if this hasn't been reported yet. Nah this was illusion ;] After putting /var/lib/pacman on separate fs (raid1) i just messed things a little and run out of inodes.
# fsck.ext2 -pfv /dev/md1 18072 inodes used (100.00%)
Most important is what pacman did. So after -Syu packages were updated and no changes in db was made. Most important is that i pacman didn't show any error msg about that.
Today i trayed -Syu again i got last time installed packages list added to new one. Pacman showed only packages list and size then just quit w/o any error again.
Now I'm trying to repair db and reproduce bug, but i think that and i can't make its 'not' work again :)
quick fix for that is to make small change in pacman that first he will tray to write db entry then packages files to disk.
Sorry for my 'bad' English i hope that all catch my drift.
Yes, this is a critical bug imho. To be short: At this moment pacman cannot rollback transaction (but it is planned: FS#8585) What is even worse (extra bug), it doesn't inform you about unsuccessful db operations (if I didn't misunderstand you); but you Now there is a nice error msg: # pacman -S perl-params-validate ... error: could not open file /var/lib/pacman/local//perl-params-validate-0.89-1/depends: No space left on device error: could not update database entry perl-params-validate-0.89-1 error: could not commit transaction error: failed to commit transaction (could not update database)
but still after: # pacman -S perl-params-validate :: perl-params-validate-0.89-1: local version is up to date. Upgrade anyway? [Y/n]
Bye Bye
On Nov 16, 2007 9:24 AM, Łukasz Wychrystenko <t0@czlug.icis.pcz.pl> wrote:
Now there is a nice error msg: # pacman -S perl-params-validate ... error: could not open file /var/lib/pacman/local//perl-params-validate-0.89-1/depends: No space left on device error: could not update database entry perl-params-validate-0.89-1 error: could not commit transaction error: failed to commit transaction (could not update database)
but still after:
# pacman -S perl-params-validate :: perl-params-validate-0.89-1: local version is up to date. Upgrade anyway? [Y/n]
What's the difference here? You only get messages on install and not upgrade? Is that correct? Also, would you mind checking pacman-git to see if any of this has changed?
Dnia Fri, 16 Nov 2007 11:06:42 -0600 "Aaron Griffin" <aaronmgriffin@gmail.com> napisał(a):
On Nov 16, 2007 9:24 AM, Łukasz Wychrystenko <t0@czlug.icis.pcz.pl> wrote:
Now there is a nice error msg: # pacman -S perl-params-validate ... error: could not open file /var/lib/pacman/local//perl-params-validate-0.89-1/depends: No space left on device error: could not update database entry perl-params-validate-0.89-1 error: could not commit transaction error: failed to commit transaction (could not update database)
but still after:
# pacman -S perl-params-validate :: perl-params-validate-0.89-1: local version is up to date. Upgrade anyway? [Y/n]
What's the difference here? You only get messages on install and not upgrade? Is that correct?
First time i got messages on sysupgrade, but i don't know how to repeat them (now after 100% of inodes usage i get this kind error so it's correct behavior, but after unsuccessfully installed package and unsuccessfully added database entry pacman giving me answer that this package is up to date, so it is uncorrected and should/will be fixed in FS#8585)
Also, would you mind checking pacman-git to see if any of this has changed? I don't know how to repeat error with -Syu (No space left error all the time)
participants (3)
-
Aaron Griffin
-
Nagy Gabor
-
Łukasz Wychrystenko