Bug 4820
Summary: | Kernel Crash & system hang if copying of file continues even no more space left | ||
---|---|---|---|
Product: | File System | Reporter: | Francism (francism501) |
Component: | XFS | Assignee: | XFS Guru (xfs-masters) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | high | CC: | bunk |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.12 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
generate termcap file on the share
copy and compare,occupy all space in the volume LVM setup |
Description
Francism
2005-06-30 01:52:50 UTC
Looks similar to an internal sgi bug, nr 927915, orignally reported at http://www.icglink.com/cluster-debug-2.html How easily can you reproduce this? Can you see if you can simplify this test case, for example by taking SAMBA out of the equation & run your copy script locally, and perhaps try a simple filesystem without lvm? It'd be good to have a simple testcase to reproduce this, thanks. (And if it does require lvm/samba, then so be it) :) Thanks, -Eric Dear Eric, This easily reproducible if system are with scsi in LVM and XFS. Also can reproduce this if samba are out of the equation. Same situation of the link that you've attached. thanks, francism So samba is not part of the testcase... do you only see it with lvm? Please go ahead & include details of your lvm setup, as well as any script you may use to fill the fs to reproduce the problem. thanks, -Eric Created attachment 5244 [details]
generate termcap file on the share
Runme first
Created attachment 5245 [details]
copy and compare,occupy all space in the volume
Created attachment 5246 [details]
LVM setup
Dear Eric, first create separate volume with xfs, then copy & run attachment(id=5244)on a volume copy & run attachment(id=5245)on a volume,this will copy file to accupy all space,please ignore any out of space messsages. keep running the script until the system will crash. also attached is my lvm config. thanks, francism Is this issue still present in kernel 2.6.19? Please reopen this bug if it's still present with kernel 2.6.20. |