Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Where does Firefox store files that should not be included in system backups (ubuntu)?

  • 1 wótegrono
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót cor-el

DinoNerd
DinoNerd
more options

My daily backups of my personal account on a ubuntu-derived system are enormous. The first problem I found was the directory .cache, full of kinds of things that change daily and don't belong in a backup. I eliminated this directory from the backups, halving their size. So far so good. But the incremental backups are still huge, even on days where I've barely used the system at all.

The next biggest questionable directory is .mozilla/firefox/05malccw.default-release and in particular .mozilla/firefox/05malccw.default-release/storage

$ du -sh .mozilla/firefox/05malccw.default-release/storage 2.2G .mozilla/firefox/05malccw.default-release/storage

It's pretty clear what program creates this and regularly changes it contents. Examining the files suggests that most or all of them are useless in a data-recovery type situation. But I'm not sure.

What's in this directory? Will the path change when I update to a new version of firefox, using normal ubuntu tools? Is there an rsync pattern I can use to identify all possible directories with this function, so as to teach my backup script to ignore not only the current directory, but the one I'll get when I next update firefox?

Are there other directories created/populated by firefox that shouldn't be in backups, besides .mozilla/firefox/05malccw.default-release/ and .cache/mozilla ?

Note that I'm on an ubuntu derivative, using the packages from the distro repositories; it's more than possible that paths are determines at build time, by the people who configure and build those packages.

My daily backups of my personal account on a ubuntu-derived system are enormous. The first problem I found was the directory .cache, full of kinds of things that change daily and don't belong in a backup. I eliminated this directory from the backups, halving their size. So far so good. But the incremental backups are still huge, even on days where I've barely used the system at all. The next biggest questionable directory is .mozilla/firefox/05malccw.default-release and in particular .mozilla/firefox/05malccw.default-release/storage $ du -sh .mozilla/firefox/05malccw.default-release/storage 2.2G .mozilla/firefox/05malccw.default-release/storage It's pretty clear what program creates this and regularly changes it contents. Examining the files suggests that most or all of them are useless in a data-recovery type situation. But I'm not sure. What's in this directory? Will the path change when I update to a new version of firefox, using normal ubuntu tools? Is there an rsync pattern I can use to identify all possible directories with this function, so as to teach my backup script to ignore not only the current directory, but the one I'll get when I next update firefox? Are there other directories created/populated by firefox that shouldn't be in backups, besides .mozilla/firefox/05malccw.default-release/ and .cache/mozilla ? Note that I'm on an ubuntu derivative, using the packages from the distro repositories; it's more than possible that paths are determines at build time, by the people who configure and build those packages.

Wšykne wótegrona (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You do not need to backup the Firefox profile folder location in ~/.cache as that secondary location only stores temporary data, only the ~/.mozilla location has important data. The storage folder is used by indexedDB (local storage) to store extension data and data for internal pages and persistent storage used by websites to store data locally. Extensions use a GUID that is saved in prefs.js in extensions.webextensions.uuids. It is up to you to decide that data in storage is important enough to backup, cleanup this folder to remove data for websites that you no longer need.