| To: | xfs-masters@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 64191] XFS log crashed when unmount - with extremely condition. |
| From: | bugzilla-daemon@xxxxxxxxxxxxxxxxxxx |
| Date: | Wed, 09 Jul 2014 04:42:56 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | xfs-masters@xxxxxxxxxxx |
| In-reply-to: | <bug-64191-470@xxxxxxxxxxxxxxxxxxxxxxxxx/> |
| References: | <bug-64191-470@xxxxxxxxxxxxxxxxxxxxxxxxx/> |
https://bugzilla.kernel.org/show_bug.cgi?id=64191 --- Comment #5 from jyhpsycho@xxxxxxxxx --- (In reply to Eric Sandeen from comment #3) > The dmesg also says: > > [848715.457943] XFS (loop3): Log size 927 blocks too small, minimum size is > 4740 blocks > [848715.465674] XFS (loop3): Log size out of supported range. Continuing > onwards, but if log hangs are > [848715.465674] experienced then please report this message in the bug > report. > > Seems that at least mkfs & the kernel should agree on the minimum log size. Right now, I can see that message. It still occurs with very recent kernel, but it explains that log size under certain blocks does not officially supported. I'll check whether this error does not occur with 4740 or more blocks of log size, and close this issue when it does not occur with officially supported log size. -- You are receiving this mail because: You are the assignee for the bug. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 79721] New: tar sometimes throws "No space left on device" error when untarring large source tree., bugzilla-daemon |
|---|---|
| Next by Date: | [Bug 79721] tar sometimes throws "No space left on device" error when untarring large source tree., bugzilla-daemon |
| Previous by Thread: | [Bug 79721] New: tar sometimes throws "No space left on device" error when untarring large source tree., bugzilla-daemon |
| Next by Thread: | Fill in the information ! CASE ID : - 47107600, Bank of Ireland Online 3 6 5 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |