You should
be able to test it with ulimit -f, that will allow you to
generate SIGXFSZ with smaller files.
This will send the backend the signal, easily.
ps auxww | grep -v grep | grep -v gdb | grep mythbackend | xargs -n1 kill
-s SIGXFSZ
This has been a problem for me - while I use XFS and thus have no large
file woes, I tend to run close to full on my hard drives, and if myth runs
out of disk space, the backend basically dies...
Ian
On Fri, 20 Jan 2006, Buzz wrote:
The problem is that as it exists now in CVS,
: [mythtv] Backend process dies at 4GB file limit?
On Wednesday 18 January 2006 11:45 pm, Louie Ilievski wrote:
How about Ext2IFS (Google for it), which is a nice, read-only
FileSystem driver for ext2/3 drives.
Or, better yet, another one also called Ext2 IFS but with a
space
How about Ext2IFS (Google for it), which is a nice, read-only
FileSystem driver for ext2/3 drives.
Or, better yet, another one also called Ext2 IFS but with a space :-) It has
full read and write support, and I have relied on it for my external hard
drive as a means to use the space in both
] Backend process dies at 4GB file limit?
-with backtrace as requested.
Mike,
Thanks for the URL tip re gdb.
In this case however, the BT I've given is enough to find the
problem/solution:
*) OS is sending a SIGXFSZ to backend, backend is taking
default action which coredump and exit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buzz wrote:
P.S. Before you tell me FAT32 is a bad, naughty, unsupported filesystem..
tell me another filesystem that works under both MS Windows and linux,
reliably, and I'll happily change (I'm waiting in anticipation of native
ext2/3 windows
Buzz wrote:
Hi All. I'm working on a solution to this thread and have got the
following steps working in my code (diff attached):
1) OS sends SIGXFSZ to mythbackend
2) backend captures said signal, squirrels it into a global called
LastSignal, so anyone who wants to can look for it.
The problem is that as it exists now in CVS, ThreadedFileWriter.cpp has no
usual failure path from the 'write' command (in safe_write). safe_write
returns a uint to indicate how much was written, and '0' is a legitimate
amount to write, not an error case. I've changed the relevant places to
Are you interested in this scenario:
Backend saves files to FAT32 partition.
Backend tries to exceed 4GB (or there abouts) while unattended.
Backend dies with error File size limit exceeded emitted by OS.
Backend's last message prior to dying was:
TFW: safe_swite() funky usleep
(message comes
: [mythtv] Backend process dies at 4GB file limit?
Are you interested in this scenario:
Backend saves files to FAT32 partition.
Backend tries to exceed 4GB (or there abouts) while unattended.
Backend dies with error File size limit exceeded emitted by OS.
Backend's last message prior
On 1/18/06, Buzz [EMAIL PROTECTED] wrote:
Are you interested in this scenario:
Backend saves files to FAT32 partition.
Backend tries to exceed 4GB (or there abouts) while unattended.
Backend dies with error File size limit exceeded emitted by OS.
Backend's last message prior to dying was:
]
[mailto:[EMAIL PROTECTED] On Behalf Of Joe Votour
Sent: Thursday, 19 January 2006 1:42 PM
To: Development of mythtv
Subject: Re: [mythtv] Backend process dies at 4GB file limit?
--- Buzz [EMAIL PROTECTED] wrote:
Are you interested in this scenario:
Backend saves files to FAT32
On Wednesday 18 January 2006 22:30, Buzz wrote:
Are you interested in this scenario:
Backend saves files to FAT32 partition.
Backend tries to exceed 4GB (or there abouts) while unattended.
Backend dies with error File size limit exceeded emitted by OS.
Backend's last message prior to dying
.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Buzz
Sent: Thursday, 19 January 2006 3:08 PM
To: 'Development of mythtv'
Subject: Re: [mythtv] Backend process dies at 4GB file limit?
Wouldn't it be reasonable if it barfed the recording
partially
January 2006 2:30 PM
To: Development of mythtv
Subject: Re: [mythtv] Backend process dies at 4GB file limit?
On Wednesday 18 January 2006 22:30, Buzz wrote:
Are you interested in this scenario:
Backend saves files to FAT32 partition.
Backend tries to exceed 4GB (or there abouts) while
Buzz wrote:
All of backend log is available on request, and gdb is still sitting there
(for a few hours anyway)
good
, incase you want me to do anything else with it.
:-) I'm a novice with GDB, so be gentle with me. (I don't know anything
more than how to do 'run','c' and 'bt'.)
Please
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael T. Dean
Sent: Thursday, 19 January 2006 4:57 PM
To: Development of mythtv
Subject: Re: [mythtv] Backend process dies at 4GB file limit?
- with backtrace as requested.
Buzz wrote:
All of backend log
On Wednesday 18 January 2006 11:45 pm, Louie Ilievski wrote:
How about Ext2IFS (Google for it), which is a nice, read-only
FileSystem driver for ext2/3 drives.
Or, better yet, another one also called Ext2 IFS but with a space :-) It
has full read and write support, and I have relied on it
18 matches
Mail list logo
