| To: | <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Journal recovery problem with 2.6.16? |
| From: | "Andrew Hall" <andrew.a.hall@xxxxxxxxx> |
| Date: | Thu, 23 Mar 2006 17:24:48 +1100 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=ggWeN2M8E7oXmIdAyIEqLjUBHmZlk7kk6v33DiOmE94t681VgUWbHq0Hi2tQPDEIaKreztOuI6/HtB4zh+Jvbryg7RYIjdXQkzk6rIUYi1lmNwKbph27dXTdPb/oANDVzPgEHuDxNhvk6yzN3xEwDlmJDMzCp65M9kcT7/MVlvc= |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Hello, Has anything changed in the Linux xfs implementation between 2.6.12 and 2.6.16 in relation to log recovery on mount? With 2.6.12 and below a mount of a dirty partition would undergo a recovery and then continue mounting successfully. The same partition (dirty) booted with a 2.6.16 image compiled today gives the error on mount: XFS mounting filesystem hda7 Starting XFS recovery on filesystem: hda7 (logdev: internal) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed: error 5 XFS: log mount failed An xfs_repair fails with "journal contains valuable metadata, please mount first". When I reboot with 2.6.12 kernel the partition mounts correctly. It seems 2.6.16 is less tolerant to unclean partition shutdowns and subsequence mounts. Is there a reason for this? thanks, Andrew. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: TAKE 951193 - XFS rewrite clustering clusters clean pages, Christian Guggenberger |
|---|---|
| Next by Date: | Journal recovery problem with 2.6.16, temp02 |
| Previous by Thread: | TAKE 904196 - fix typos, Nathan Scott |
| Next by Thread: | Journal recovery problem with 2.6.16, temp02 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |