The attached patch should fix the problem, which is that mkdosfs needs to be compiled with large file support.
diff -ru dosfstools-2.11/debian/changelog dosfstools-2.11.patched/debian/changelog --- dosfstools-2.11/debian/changelog 2005-03-20 12:49:35.627270352 +0200 +++ dosfstools-2.11.patched/debian/changelog 2005-03-20 12:51:05.153660272 +0200 @@ -1,3 +1,10 @@ +dosfstools (2.11-1.1) unstable; urgency=low + + * debian/rules: Added $(getconf LFS_CFLAGS) to OPTFLAGS so that volumes + larger than 1 gigabyte (or 2 giga-sectors) will work. Closes: #300126. + + -- Lars Wirzenius <[EMAIL PROTECTED]> Sun, 20 Mar 2005 12:39:00 +0200 + dosfstools (2.11-1) unstable; urgency=low * New upstream version (Closes: #293394, #295181, #294177, #270023, #258402, diff -ru dosfstools-2.11/debian/rules dosfstools-2.11.patched/debian/rules --- dosfstools-2.11/debian/rules 2005-03-20 12:49:35.627270352 +0200 +++ dosfstools-2.11.patched/debian/rules 2005-03-20 12:48:13.479758672 +0200 @@ -22,9 +22,9 @@ ARCH = $(shell dpkg --print-gnu-build-architecture) ifeq ($(ARCH),alpha) -OPTFLAGS="-fomit-frame-pointer -fno-strict-aliasing" +OPTFLAGS="-fomit-frame-pointer -fno-strict-aliasing $(shell getconf LFS_CFLAGS)" else -OPTFLAGS="-O2 -fomit-frame-pointer" +OPTFLAGS="-O2 -fomit-frame-pointer $(shell getconf LFS_CFLAGS)" endif build:
