search for: enospac

...39;t see any different between mixed and defaults blocks. So using mixed blocks have sense? Or this is outdated function? Can i change in future type of chunk allocation between mixed and default (with using balance function)? i believe in mixed blocks because this function can awoid problems with ENOSPACE error (when system can''t allocated metadata chunk) and can up space utilization on the disk. On slow hdd, we no see any different between profiles, and on speed ssd perfomance penalty should not be significant. (i just using btrfs on my PC (1 TB hdd) and laptop (ssd 128 GB), i like this...

...id tftp_recvfile(const struct formats *pf, struct tftphdr *oap, int oac syslog(LOG_WARNING, "tftpd: write(ack): %m"); goto abort; } - write_behind(file, pf->f_convert); + if(write_behind(file, pf->f_convert) < 0) { + nak(ENOSPACE, NULL); + (void)fclose(file); + goto abort; + } for (;;) { n = recv_time(peer, dp, PKTSIZE, 0, &r_timeout); if (n < 0) { /* really? */ @@ -1712,7 +1716,11 @@ static void tftp_recvfile(const struct formats *pf, struct tft...

...in.html#elementsDisks The attribute is called "error_policy". The documentation says: The optional error_policy attribute controls how the hypervisor will behave on a disk read or write error, possible values are "stop", "report", "ignore", and "enospace".Since 0.8.0, "report" since 0.9.7 The default setting of error_policy is "report". There is also an optional rerror_policy that controls behavior for read errors only. Since 0.9.7. If no rerror_policy is given, error_policy is used for both read and write errors....

...it would have helped me in this case. Will take a look at this. Sebastian --- tftp-hpa-5.2/tftpd/tftpd.c.orig 2015-01-16 21:45:30.790798281 +0100 +++ tftp-hpa-5.2/tftpd/tftpd.c 2015-01-18 23:44:28.031177383 +0100 @@ -1504,6 +1504,8 @@ static int validate_access(char *filenam return ENOSPACE; case EEXIST: return EEXISTS; + case EACCES: + return EACCESS; default: return errno + 100; }

On 01/18/2015 03:23 PM, Sebastian Herbszt wrote: > > --- tftp-hpa-5.2/tftpd/tftpd.c.orig 2015-01-16 21:45:30.790798281 +0100 > +++ tftp-hpa-5.2/tftpd/tftpd.c 2015-01-18 23:44:28.031177383 +0100 > @@ -1504,6 +1504,8 @@ static int validate_access(char *filenam > return ENOSPACE; > case EEXIST: > return EEXISTS; > + case EACCES: > + return EACCESS; > default: > return errno + 100; > } I can't remember, but I have a vague recollection that someone specifically requested that EA...

Hi, On 01/17/2015 12:57 AM, Sebastian Herbszt wrote: >> On 01/16/2015 12:19 AM, Sebastian Herbszt wrote: >>> Andreas Gruenbacher wrote: >>>> "Loading <FILE>... failed: No such file or directory" when the TFTP >>>> server replies with "Permission denied" for the kernel or initrd. >>> [...] >>> >>> The

I recently upgraded from 7.1 to 7.2 and told it to upgrade my root filesystem (5gig) to Ext3. A while after that, I ran out of space. Directly after upgrading I had approximately 1.2gig free space. Thinking that I needed more space, I proceeded to create 3 extended partitions for /home, /usr and /tmp. Mounted them in /mnt, copied files..etc. All of these filesystems were left as ext2.

...id tftp_recvfile(const struct formats *pf, struct tftphdr *oap, int oac syslog(LOG_WARNING, "tftpd: write(ack): %m"); goto abort; } - write_behind(file, pf->f_convert); + if(write_behind(file, pf->f_convert) < 0) { + nak(ENOSPACE, NULL); + (void)fclose(file); + goto abort; + } for (;;) { n = recv_time(peer, dp, PKTSIZE, 0, &r_timeout); if (n < 0) { /* really? */ @@ -1712,7 +1716,11 @@ static void tftp_recvfile(const struct formats *pf, struct tft...

...script storage driver framework entailed large changes in this plugin, so many of these problems were addressed implicitly. Hopefully, all problems are solved now. Changelog v0.4.4: * Added support for Japanese mail addresses with dots at non-standard places in localpart. * Changed handling of ENOSPACE into a normal temporary failure and added handling of ENOQUOTA as a user error. * Restructured result execution, so that all actions which involve mail storage are always committed before all others. + Implemented support for generic Sieve storages. Using alternative storages now also possib...

...script storage driver framework entailed large changes in this plugin, so many of these problems were addressed implicitly. Hopefully, all problems are solved now. Changelog v0.4.4: * Added support for Japanese mail addresses with dots at non-standard places in localpart. * Changed handling of ENOSPACE into a normal temporary failure and added handling of ENOQUOTA as a user error. * Restructured result execution, so that all actions which involve mail storage are always committed before all others. + Implemented support for generic Sieve storages. Using alternative storages now also possib...

Hi, We hit an interesting issue with Ext3 in ordered data mode. A large file was truncated (open with O_TRUNC) and immediately over-written with a single write call. The write call returned ENOSPACE, but a check for space (using essentially statfs) promised that there would be plenty of space. The reason turned out to be that the blocks freed by the truncation were not yet available to the write because the transaction had not committed. The total number of blocks write required in additio...

...ctx->failed = TRUE; + mail_storage_set_critical(STORAGE(ctx->mbox->storage), + "utime(%s) failed: %m", new_path); + } + } + } else { ret = -1; if (ENOSPACE(errno)) { mail_storage_set_error(STORAGE(ctx->mbox->storage), @@ -332,18 +343,6 @@ t_push(); path = t_strconcat(ctx->tmpdir, "/", ctx->files->basename, NULL); - if (ctx->received_date != (time_t)-1) { - /* set...

RFC: This is draft proposal API for the user-level interface for feeds. (This does not describe changelogs in general). Feeds would generally be used for two things: creating audit logs, and driving a database watching for filesystem changes. -------------- next part -------------- A non-text attachment was scrubbed... Name: feed_api.pdf Type: application/pdf Size: 85313 bytes Desc: not

...xternal disk, however, 2.6.38.8 preferred the faster but smaller internal disks, and it would happily fill them up with the large, long-term storage data that was meant to remain mostly in the external disk (as 3.0 would have done), leaving no room for raid1 metadata allocations. I''d get -ENOSPACE errors every now and again while copying data onto this filesystem, even though there was plenty of available space, and even plenty of available space in already-allocated metadata block groups. So much so that retrying the same copies after a few seconds would succeed. Oh well... That''...

...... OK 100) QEMU XML-2-ARGV disk-drive-cache-v1-wb ... OK 101) QEMU XML-2-ARGV disk-drive-cache-v1-none ... OK 102) QEMU XML-2-ARGV disk-drive-error-policy-stop ... OK 103) QEMU XML-2-ARGV disk-drive-error-policy-enospace ... OK 104) QEMU XML-2-ARGV disk-drive-error-policy-wreport-rignore ... OK 105) QEMU XML-2-ARGV disk-drive-cache-v2-wt ... OK 106) QEMU XML-2-ARGV disk-drive-cache-v2-wb ... OK 107) QEMU XML-2-ARGV disk-drive-cache-v2...

Hi everyone, I described the reflink operation at the Linux Storage & Filesystems Workshop last month. Originally implemented as an ocfs2-specific ioctl, the consensus was that it should be a syscall from the get-go. Here's some first-cut patches. For people who have not seen reflink, either at LSF or on the ocfs2 wiki, the first patch contains Documentation/filesystems/reflink.txt to